Hi Romain, On Wed, May 24, 2017 at 11:05 AM, Romain Perier <[email protected]> wrote: > Le 24/05/2017 à 16:55, Trevor Woerner a écrit : >> On Wed, May 24, 2017 at 10:46 AM, Romain Perier >> <[email protected]> wrote: >>> Le 22/05/2017 à 18:08, Trevor Woerner a écrit : >>>> u-boot 2017.05 was released May 10. Wouldn't it be better to update >>>> oe-core's u-boot to 2017.05 then just add any differences in >>>> meta-rockchip? >>> Good idea yes. I will bump u-boot-common_${PV} and u-boot_2017.01 to >>> v2017.05 in poky (and then propose changes in meta-rockchip) >> Changes to u-boot should be sent to openembedded-core; poky gets >> updated from there (not vice versa). > Even, if I Cc: the ML oe-core and yocto ? (so I have to do the changes > in oe-core directly, I mean the repo. right ?)
Yes. The "home" of the u-boot recipe is in openembedded-core. Please send any updates/changes to the u-boot recipe to the openembedded-core mailing list [http://lists.openembedded.org/mailman/listinfo/openembedded-core]. CC'ing it to other lists would not be polite since most OE/Yocto lists receive quite a lot of traffic already and this would be a non-relevant email to them. Poky is derived from a bunch of sources, primarily openembedded-core, plus some small additions of its own. Only when you want to change one of these small additions would you send a patch to the poky mailing list directly (which isn't the case with u-boot). -- _______________________________________________ yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/yocto
