On Sun, 2 Oct 2022 16:36:39 +0200 Crt Mori <cmo@xxxxxxxxxxx> wrote: > >> I sure hope you mean 6.1 material... It would be great to get into 6.0 > >> as i think that is a most likely candidate also for Android kernel > >> baseline (which is what I am also targeting). > > > > Sorry, I do mean 6.2. > > > > The merge window for 6.0 was months ago and we have to line 6.1 material > > up a week or so before the 6.1 merge window (which probably starts today). > > That allows us to get build bots and similar results before the merge window > > and with time to fix any issues. > > > > So unfortunately this will only be in a released kernel in about 6 months time: > > 3 months for the 6.1 cycle that this just missed and then it'll go into Linus' > > mainline tree, but the release will still be 3 months after that. > > > > In the meantime it'll be in linux-next from just after 6.1-rc1, and in > > Linus' tree for 6.2-rc1. > > > > Kernel cycles are short for a bit project, but they still have about > > 3 to 6 month delay for new code reaching a release. This just happened > > to hit the maximum. > > > > Jonathan > > OK, then fingers crossed we get rc8, as then I imagine you could put > this series into the 6.1 right? Would be really grateful if it would > not take 6 months to get this into mainline. Pretty unlikely as last Sunday Linus indicated that he was expecting to release new kernel today :( Note it'll be in mainline in 3 months, just not in a release because those take just under 3 months. Jonathan > > Crt > > On Sun, 2 Oct 2022 at 13:25, Jonathan Cameron <jic23@xxxxxxxxxx> wrote: > > > > On Mon, 26 Sep 2022 15:20:16 +0200 > > Crt Mori <cmo@xxxxxxxxxxx> wrote: > > > > > On Sat, 24 Sept 2022 at 18:32, Jonathan Cameron <jic23@xxxxxxxxxx> wrote: > > > > > > > > > The sensor runtime suspension is set to MLX90632_SLEEP_DELAY_MS which is > > > > > hardcoded to 3 times as much as MEAS_MAX_TIME. > > > > > > > > > Hi Crt, > > > > > > > > Applied. However, we are cutting it very tight for the coming merge window > > > > so I'm not sure I'll get a 3rd pull request out (this just missed the 2nd > > > > one as I only queued up material that was in a final state last weekend) > > > > So for now pushed out as testing and we'll see if Linus hints at an rc8 > > > > when he releases rc7 tomorrow. If not this will be 6.2 material now. > > > > > > > I sure hope you mean 6.1 material... It would be great to get into 6.0 > > > as i think that is a most likely candidate also for Android kernel > > > baseline (which is what I am also targeting). > > > > Sorry, I do mean 6.2. > > > > The merge window for 6.0 was months ago and we have to line 6.1 material > > up a week or so before the 6.1 merge window (which probably starts today). > > That allows us to get build bots and similar results before the merge window > > and with time to fix any issues. > > > > So unfortunately this will only be in a released kernel in about 6 months time: > > 3 months for the 6.1 cycle that this just missed and then it'll go into Linus' > > mainline tree, but the release will still be 3 months after that. > > > > In the meantime it'll be in linux-next from just after 6.1-rc1, and in > > Linus' tree for 6.2-rc1. > > > > Kernel cycles are short for a bit project, but they still have about > > 3 to 6 month delay for new code reaching a release. This just happened > > to hit the maximum. > > > > Jonathan > > > > > > > > > > > Thanks, > > > > > > > > Jonathan > > > > > > > > > >
