From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guenter Roeck <linux@roeck-us.net>
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
Subject: Re: [PATCH 6.1 00/13] 6.1.38-rc2 review
Date: Wed, 5 Jul 2023 17:06:02 +0100 [thread overview]
Message-ID: <2023070529-barcode-unpleased-5705@gregkh> (raw)
In-Reply-To: <824705ec-38ca-1587-573c-595b146ee2e1@roeck-us.net>
On Wed, Jul 05, 2023 at 07:23:30AM -0700, Guenter Roeck wrote:
> On 7/4/23 01:48, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 6.1.38 release.
> > There are 13 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, 06 Jul 2023 08:46:01 +0000.
> > Anything received after that time might be too late.
> >
> > The whole patch series can be found in one patch at:
> > https://www.kernel.org/pub/linux/kernel/v6.x/stable-review/patch-6.1.38-rc2.gz
> > or in the git tree and branch at:
> > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.1.y
> > and the diffstat can be found below.
> >
> > thanks,
> >
> > greg k-h
> >
> > -------------
> > Pseudo-Shortlog of commits:
> >
> > Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > Linux 6.1.38-rc2
> >
> > Linus Torvalds <torvalds@linux-foundation.org>
> > gup: avoid stack expansion warning for known-good case
> >
>
> I am a bit puzzled by this patch. It avoids a warning introduced with
> upstream commit a425ac5365f6 ("gup: add warning if some caller would
> seem to want stack expansion"), or at least it says so, but that patch
> is not in v6.1.y. Why is this patch needed here ?
It isn't, and was dropped for -rc2, right?
thanks,
greg k-h
next prev parent reply other threads:[~2023-07-05 16:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 8:48 [PATCH 6.1 00/13] 6.1.38-rc2 review Greg Kroah-Hartman
2023-07-04 11:27 ` ogasawara takeshi
2023-07-05 6:58 ` Bagas Sanjaya
2023-07-05 7:08 ` Conor Dooley
2023-07-05 8:11 ` Ron Economos
2023-07-05 14:23 ` Guenter Roeck
2023-07-05 16:06 ` Greg Kroah-Hartman [this message]
2023-07-05 16:13 ` Guenter Roeck
2023-07-05 16:25 ` Greg Kroah-Hartman
2023-07-05 16:29 ` Guenter Roeck
2023-07-05 14:43 ` Markus Reichelt
2023-07-05 16:28 ` Guenter Roeck
2023-07-06 10:23 ` Chris Paterson
2023-07-10 14:25 ` Jon Hunter
-- strict thread matches above, loose matches on Subject: below --
2023-07-05 16:40 Daniel Díaz
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=2023070529-barcode-unpleased-5705@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.