No updates in rolling branches

No updates in rolling branches

[Acid Bong]

Hi there, hello,

I noticed that v6.5.2 already has patches that are not passed to v6.4.y, but it's still not merged into `rolling-stable`. Do you not merge 6.5.y until 6.4.15 comes to its EOL? Or haven't pushed the merge?

(re-sent, as suggested by your email bot)

Regards,
~acidbong

Re: No updates in rolling branches

[Greg KH]

On Tue, Sep 12, 2023 at 01:40:47PM +0300, Acid Bong wrote:
> Hi there, hello,
> 
> I noticed that v6.5.2 already has patches that are not passed to
> v6.4.y, but it's still not merged into `rolling-stable`. Do you not
> merge 6.5.y until 6.4.15 comes to its EOL? Or haven't pushed the
> merge?

We normally move to the "next" stable release for that rolling target
when the number of reports has dropped off and all looks good.  That
usually lines up with the EOL time as well.  So that means we'll
probably move this later this week.

You are always free to move to the latest release kernel if you want
sooner :)

thanks,

greg k-h

No updates in rolling branches

[Acid Bong]

Hi there, hello,

I've noticed that the recent (at the moment) releases 6.2.10 and 6.1.23 weren't merged into linux-rolling-stable and linux-rolling-lts respectively. Is there something wrong with them that they require the delay?

Kind regards,
~acidbong

Re: No updates in rolling branches

[Greg KH]

On Mon, Apr 10, 2023 at 11:36:41AM +0300, Acid Bong wrote:
> Hi there, hello,
> 
> I've noticed that the recent (at the moment) releases 6.2.10 and
> 6.1.23 weren't merged into linux-rolling-stable and linux-rolling-lts
> respectively. Is there something wrong with them that they require the
> delay?

Sorry about that, I just forgot to push them out.  They should now be
there (might take a bit for the backend mirrors to sync.)

thanks,

greg k-h

Re: No updates in rolling branches

[Acid Bong]

Hey, we all are human beings.

The merges are already available, thank you.

Cheers and good luck,
~acidbong