No need to be nervous. The patch will make it in; patches do not get quietly rejected. If it hasn't showed up yet, it's most likely because the patch will be tested on the autobuilder in a separate set from the 'regular patches', or (yes, this happens) it has slipped through the cracks. In that case (I know it's impossible to tell from the outside), just resend again.
Also, please do help us out with oe-core patch review and recipe maintenance, particularly updating them to latest versions. Alex 2018-06-14 16:57 GMT+03:00 Stefan Agner <ste...@agner.ch>: > On 04.06.2018 18:18, Alexander Kanavin wrote: >> On 06/04/2018 07:06 PM, Stefan Agner wrote: >> >>> Anything holding us back merging this changes? >> >> Please read the Yocto project status mail: >> >> " · Patch review/merging was slow over the past week due to >> Ross being on vacation and changes in Richard’s employment/hardware >> situation but at least some of the backlog was resolved over the >> weekend and the hardware issues should be worked around now." >> > > Gentle ping on that again. > > This week it read: > "Due to the milestone, patch merging is slowing to stabilize." > > Also, there have been patches merged which were posted after this > patchset... It is really rather important for us since it is hard to fix > in lower layers... > > So I am getting nervous whether it still makes it? > > -- > Stefan > -- > _______________________________________________ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-core -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
