From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Pavel Machek <pavel@denx.de>
Cc: Florian Fainelli <f.fainelli@gmail.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,
jonathanh@nvidia.com, sudipm.mukherjee@gmail.com,
srw@sladewatkins.net, rwarsow@gmx.de, conor@kernel.org,
hargar@microsoft.com, broonie@kernel.org
Subject: Re: [PATCH 6.1 000/569] 6.1.129-rc2 review
Date: Mon, 12 May 2025 11:31:20 +0200 [thread overview]
Message-ID: <2025051205-return-blame-ba79@gregkh> (raw)
In-Reply-To: <aCG9kFjnZrMd4sy8@duo.ucw.cz>
On Mon, May 12, 2025 at 11:21:20AM +0200, Pavel Machek wrote:
> On Sat 2025-02-22 10:39:23, Greg Kroah-Hartman wrote:
> > On Sat, Feb 22, 2025 at 10:21:18AM +0100, Pavel Machek wrote:
> > > On Sat 2025-02-22 07:28:10, Greg Kroah-Hartman wrote:
> > > > On Fri, Feb 21, 2025 at 09:45:15AM -0800, Florian Fainelli wrote:
> > > > >
> > > > >
> > > > > On 2/20/2025 2:57 AM, Greg Kroah-Hartman wrote:
> > > > > > This is the start of the stable review cycle for the 6.1.129 release.
> > > > > > There are 569 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 Sat, 22 Feb 2025 10:44:04 +0000.
> > > > > > Anything received after that time might be too late.
> > > > >
> > > > > And yet there was a v6.1.29 tag created already?
> > > >
> > > > Sometimes I'm faster, which is usually the case for -rc2 and later, I go
> > > > off of the -rc1 date if the people that had problems with -rc1 have
> > > > reported that the newer -rc fixes their reported issues.
> > >
> > > Well, quoting time down to second then doing something completely
> > > different is quite confusing. Please fix your scripts.
> >
> > Patches gladly welcome :)
>
> It is not okay to send misleading emails just because script generated
> them.
*plonk*
next prev parent reply other threads:[~2025-05-12 9:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-20 10:57 [PATCH 6.1 000/569] 6.1.129-rc2 review Greg Kroah-Hartman
2025-02-20 13:51 ` Mark Brown
2025-02-20 18:01 ` Hardik Garg
2025-02-20 19:57 ` Pavel Machek
2025-02-20 20:45 ` Slade Watkins
2025-02-21 11:04 ` Peter Schneider
2025-02-21 11:53 ` Jon Hunter
2025-02-21 17:45 ` Florian Fainelli
2025-02-22 6:28 ` Greg Kroah-Hartman
2025-02-22 9:21 ` Pavel Machek
2025-02-22 9:39 ` Greg Kroah-Hartman
2025-02-22 9:46 ` Pavel Machek
2025-05-12 9:21 ` Pavel Machek
2025-05-12 9:31 ` Greg Kroah-Hartman [this message]
2025-05-12 9:55 ` Pavel Machek
2025-02-24 8:10 ` Naresh Kamboju
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=2025051205-return-blame-ba79@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=hargar@microsoft.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