From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Lee Jones <lee@kernel.org>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
torvalds@linux-foundation.org, stable@vger.kernel.org,
lwn@lwn.net, jslaby@suse.cz
Subject: Re: Linux 5.15.104
Date: Mon, 22 May 2023 17:23:00 +0100 [thread overview]
Message-ID: <2023052236-passivism-equate-5cb8@gregkh> (raw)
In-Reply-To: <20230522102355.GA2009088@google.com>
On Mon, May 22, 2023 at 11:23:55AM +0100, Lee Jones wrote:
> On Wed, 22 Mar 2023, Greg Kroah-Hartman wrote:
>
> > I'm announcing the release of the 5.15.104 kernel.
> >
> > All users of the 5.15 kernel series must upgrade.
> >
> > The updated 5.15.y git tree can be found at:
> > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-5.15.y
> > and can be browsed at the normal kernel.org git web browser:
> > https://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=summary
> >
> > thanks,
> >
> > greg k-h
> >
> > ------------
>
> [...]
>
> > Budimir Markovic (1):
> > perf: Fix check before add_event_to_groups() in perf_group_detach()
>
> Anyone know why this didn't make it into v5.10 with it's friends?
>
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=80102f2ee715ab07be476df443bba388d5458fd1
That's a merge point, how can that go into stable kernels?
What specific commits are you thinking were missed?
thanks,
greg k-h
next prev parent reply other threads:[~2023-05-22 16:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 18:53 Linux 5.15.104 Greg Kroah-Hartman
2023-03-22 18:53 ` Greg Kroah-Hartman
2023-05-22 10:23 ` Lee Jones
2023-05-22 16:23 ` Greg Kroah-Hartman [this message]
2023-05-22 16:28 ` Lee Jones
2023-05-22 16:48 ` Greg Kroah-Hartman
2023-05-23 9:11 ` Lee Jones
2023-05-26 16:40 ` Greg Kroah-Hartman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2023052236-passivism-equate-5cb8@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=jslaby@suse.cz \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox