From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guenter Roeck <linux@roeck-us.net>, chuck.lever@oracle.com
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, shuah@kernel.org,
patches@kernelci.org, lkft-triage@lists.linaro.org,
pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
conor@kernel.org, allen.lkml@gmail.com, broonie@kernel.org
Subject: Re: [PATCH 5.10 000/770] 5.10.220-rc1 review
Date: Tue, 25 Jun 2024 17:04:10 +0200 [thread overview]
Message-ID: <2024062543-magnifier-licking-ab9e@gregkh> (raw)
In-Reply-To: <e8c38e1c-1f9a-47e2-bdf5-55a5c6a4d4ec@roeck-us.net>
On Tue, Jun 25, 2024 at 07:48:00AM -0700, Guenter Roeck wrote:
> On 6/18/24 05:27, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.10.220 release.
> > There are 770 patches in this series, all will be posted as a response
> > to this one. If anyone has any issues with these being applied, please
> > let me know.
> >
> > Responses should be made by Thu, 20 Jun 2024 12:32:00 +0000.
> > Anything received after that time might be too late.
> >
>
> [ ... ]
> > Chuck Lever <chuck.lever@oracle.com>
> > SUNRPC: Prepare for xdr_stream-style decoding on the server-side
> >
> The ChromeOS patches robot reports a number of fixes for the patches
> applied in 5.5.220. This is one example, later fixed with commit
> 90bfc37b5ab9 ("SUNRPC: Fix svcxdr_init_decode's end-of-buffer
> calculation"), but there are more. Are those fixes going to be
> applied in a subsequent release of v5.10.y, was there a reason to
> not include them, or did they get lost ?
I saw this as well, but when I tried to apply a few, they didn't, so I
was guessing that Chuck had merged them together into the series.
I'll defer to Chuck on this, this release was all his :)
thanks,
greg k-h
next prev parent reply other threads:[~2024-06-25 15:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-18 12:27 [PATCH 5.10 000/770] 5.10.220-rc1 review Greg Kroah-Hartman
2024-06-18 12:27 ` [PATCH 5.10 004/770] nfsd/nfs3: remove unused macro nfsd3_fhandleres Greg Kroah-Hartman
2024-06-18 21:01 ` [PATCH 5.10 000/770] 5.10.220-rc1 review Jon Hunter
2024-06-19 8:51 ` Pavel Machek
2024-06-19 9:04 ` Dominique Martinet
2024-06-19 10:16 ` Florian Fainelli
2024-06-19 11:10 ` Naresh Kamboju
2024-06-25 14:48 ` Guenter Roeck
2024-06-25 15:04 ` Greg Kroah-Hartman [this message]
2024-06-25 15:13 ` Chuck Lever III
2024-06-25 16:29 ` Guenter Roeck
2024-06-25 19:08 ` Chuck Lever III
2024-06-25 19:35 ` Guenter Roeck
2024-06-25 19:40 ` Chuck Lever III
2024-06-25 19:49 ` Chuck Lever III
2024-06-25 20:43 ` Guenter Roeck
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=2024062543-magnifier-licking-ab9e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=allen.lkml@gmail.com \
--cc=broonie@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@denx.de \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=srw@sladewatkins.net \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--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