From: Alyssa Ross <hi@alyssa.is>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Conor.Dooley@microchip.com, stable@vger.kernel.org,
patches@lists.linux.dev, linux-kernel@vger.kernel.org,
torvalds@linux-foundation.org, akpm@linux-foundation.org,
linux@roeck-us.net, 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
Subject: Re: [PATCH 6.2 000/138] 6.2.12-rc2 review
Date: Wed, 19 Apr 2023 13:57:05 +0000 [thread overview]
Message-ID: <20230419135705.phaf4qmqhorwx3jd@x220> (raw)
In-Reply-To: <2023041957-sector-purposely-859f@gregkh>
[-- Attachment #1: Type: text/plain, Size: 1926 bytes --]
On Wed, Apr 19, 2023 at 03:17:13PM +0200, Greg KH wrote:
> On Wed, Apr 19, 2023 at 12:26:26PM +0000, Conor.Dooley@microchip.com wrote:
> > On 19/04/2023 10:40, Greg Kroah-Hartman wrote:
> > > EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> > >
> > > This is the start of the stable review cycle for the 6.2.12 release.
> > > There are 138 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 Fri, 21 Apr 2023 09:36:26 +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.2.12-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.2.y
> > > and the diffstat can be found below.
> > >
> > > thanks,
> > >
> > > greg k-h
> >
> >
> > > Alyssa Ross <hi@alyssa.is>
> > > purgatory: fix disabling debug info
> > >
> > > Heiko Stuebner <heiko.stuebner@vrull.eu>
> > > RISC-V: add infrastructure to allow different str* implementations
> >
> > Lore is ~dead for me right now, but there should be a custom backport of
> > Alyssa's commit, submitted by her, here:
> > https://lore.kernel.org/all/20230417134044.1821014-1-hi@alyssa.is/
> >
> > Perhaps the reason is just the quantity of email, but that was
> > submitted against the "fail" email (and within a few hours), so why
> > was another commit pulled back instead of using what she provided?
>
> Ok, now both dropped, this got confusing fast.
So what's my next step to getting my patch backported?
Do I have to wait for these kernels to be released, and then submit my
backport again and hope it gets selected the second time round?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-04-19 13:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 9:40 [PATCH 6.2 000/138] 6.2.12-rc2 review Greg Kroah-Hartman
2023-04-19 12:26 ` Conor.Dooley
2023-04-19 13:17 ` Greg KH
2023-04-19 13:57 ` Alyssa Ross [this message]
2023-04-19 14:54 ` Greg KH
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=20230419135705.phaf4qmqhorwx3jd@x220 \
--to=hi@alyssa.is \
--cc=Conor.Dooley@microchip.com \
--cc=akpm@linux-foundation.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--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