Mirror of git.yoctoproject.org/poky https://git.enea.com/cgit/linux/poky.git/atom?h=nanbield-4.3 2023-10-09T14:52:17+00:00 2023-10-09T14:52:17+00:00 Lee Chee Yang chee.yang.lee@intel.com 2023-10-06T04:08:36+00:00 urn:sha1:4e2d3a987627e21ca74d561401a4b2bb6a7bf9d5 (From yocto-docs rev: ceb1812e63b9fac062f886c2a1dde23137c0e1ed) Signed-off-by: Lee Chee Yang <chee.yang.lee@intel.com> Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2023-10-09T14:52:17+00:00 Joshua Watt JPEWhacker@gmail.com 2023-09-28T18:26:16+00:00 urn:sha1:9f64aa4afce52c9b50499e6c0a4e56732f9a800a Adds an additional note about some of the side effects that can occur if recipes are not reproducible and hash equivalence is enabled. (From yocto-docs rev: 1ccc8eefe21bc432c903bb245bd0dab06e67cc14) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2023-10-09T14:52:17+00:00 Trevor Gamblin tgamblin@baylibre.com 2023-10-03T15:17:41+00:00 urn:sha1:ced8fd6ea97947d3f52e3b46fbd5de9ab207d89d The proper way to inherit the testimage class is now IMAGE_CLASSES += "testimage" so change lines with 'INHERIT += "testimage"' to match. This makes the dev-manual consistent with the migration guide, which already specifies that the old way causes an error. (From yocto-docs rev: 2a3e2c6e48be6f7ec2b3ff0817144dd1036961ba) Signed-off-by: Trevor Gamblin <tgamblin@baylibre.com> Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2023-10-09T14:52:16+00:00 Michael Opdenacker michael.opdenacker@bootlin.com 2023-10-03T19:44:11+00:00 urn:sha1:a5896803e787f5a5b5e491bb56deea50c2d2b4cb According to https://wiki.yoctoproject.org/wiki/Releases (From yocto-docs rev: 88348eb6eaa589a735b35b8ee726b9523f46e54f) Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2023-09-25T13:37:26+00:00 Roland Hieber rhi@pengutronix.de 2023-09-22T10:00:06+00:00 urn:sha1:8815eefb0d6218661794a58008e1144a77d3394f Suggested-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Suggested-by: Alexander Kanavin <alex.kanavin@gmail.com> (From yocto-docs rev: 4924c900582aaa803b003e10e48fc4a4373f6a77) Signed-off-by: Roland Hieber <rhi@pengutronix.de> Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2023-09-25T13:37:26+00:00 Roland Hieber rhi@pengutronix.de 2023-09-22T10:00:05+00:00 urn:sha1:f60c81287e916755496081d017d02aa14cb0d24c This is in accordance with the gatesgarth Release Notes: > In the ``Upstream-Status`` header convention for patches, > ``Accepted`` has | been replaced with ``Backport`` as these almost > always mean the same thing i.e. the patch is already upstream and > may need to be removed in a future recipe upgrade. If you are adding > these headers to your own patches then use Backport to indicate that > the patch has been sent upstream. <https://docs.yoctoproject.org/migration-guides/migration-3.2.html#miscellaneous-changes> Suggested-by: Michael Opdenacker <michael.opdenacker@bootlin.com> (From yocto-docs rev: 61813da94595a6e57c5fb5015229d601a558f299) Signed-off-by: Roland Hieber <rhi@pengutronix.de> Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2023-09-25T13:37:26+00:00 Roland Hieber rhi@pengutronix.de 2023-09-22T10:00:04+00:00 urn:sha1:3dc1dbc22fe7d2468675628d414f689673c72edf It was never really clear what all those reasons really meant, and every patch submitted upstream liftens the maintenance on the Yocto side. So remove the current list, and replace it with two reasons in which an upstream submission likely won't benefit the upstream project. Suggested-by: Alexander Kanavin <alex.kanavin@gmail.com> (From yocto-docs rev: 7e630fdb98e1a28abb09c8f24c90ada0a4a1b9f3) Signed-off-by: Roland Hieber <rhi@pengutronix.de> Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2023-09-25T13:37:26+00:00 Roland Hieber rhi@pengutronix.de 2023-09-22T10:00:03+00:00 urn:sha1:975e974eb1b67e93d5c36492af373c0aa46d206f This was previously included in the OpenEmbedded wiki page [1], but was not ported along with the rest in commit 95c9a1e1e78bbfb82ade (2023-09-12, Michael Opdenacker: "contributor-guide: recipe-style-guide: add Upstream-Status"). [1]: https://www.openembedded.org/index.php?title=Commit_Patch_Message_Guidelines&oldid=10935 Group the examples in their own sections (but name it differently from any other section in this document so that sphinx doesn't generate a warning about duplicate labels). (From yocto-docs rev: 3022caa35efc28d16dea81bc81ecb48998c8f3b8) Signed-off-by: Roland Hieber <rhi@pengutronix.de> Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2023-09-25T13:37:26+00:00 Roland Hieber rhi@pengutronix.de 2023-09-22T10:00:02+00:00 urn:sha1:653ac666c430c37c32df1b9e633c68214003e85c (From yocto-docs rev: a2904fd3ccdcb1d7232adce51966749cb1e3cb92) Signed-off-by: Roland Hieber <rhi@pengutronix.de> Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2023-09-25T13:37:26+00:00 Michael Opdenacker michael.opdenacker@bootlin.com 2023-09-21T08:26:24+00:00 urn:sha1:bb440f76a9349a5bb8d434fcad13df626b2a21a0 (From yocto-docs rev: 22c445e9803f5e1ac97d1efaf7ac2ea6fc2f7594) Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>