From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Pavel Machek <pavel@denx.de>
Cc: 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, 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 6.1 000/192] 6.1.110-rc1 review
Date: Tue, 10 Sep 2024 12:44:36 +0200 [thread overview]
Message-ID: <2024091051-blooper-comply-47d3@gregkh> (raw)
In-Reply-To: <ZuAhCgJ3LUBROwBR@duo.ucw.cz>
On Tue, Sep 10, 2024 at 12:35:54PM +0200, Pavel Machek wrote:
> Hi!
>
> > This is the start of the stable review cycle for the 6.1.110 release.
> > There are 192 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.
>
> Can you quote git hash of the 6.1.110-rc1?
Nope! We create the git trees for those that want throw-away trees,
once I create them I automatically delete them so I don't even know the
hash anymore.
> We do have
>
> Linux 6.1.110-rc1 (244a97bb85be)
> Greg Kroah-Hartman authored 1 day ago
>
> passing tests
>
> https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/tree/linux-6.1.y
>
> . But that's 1 day old.
Lots have changed since then, please use the latest.
thanks,
greg k-h
next prev parent reply other threads:[~2024-09-10 10:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-10 9:30 Greg Kroah-Hartman
2024-09-10 10:35 ` Pavel Machek
2024-09-10 10:44 ` Greg Kroah-Hartman [this message]
2024-09-10 21:18 ` Pavel Machek
2024-09-10 12:54 ` Naresh Kamboju
2024-09-10 14:35 ` Naresh Kamboju
2024-09-11 12:54 ` Greg Kroah-Hartman
2024-09-10 18:55 ` Florian Fainelli
2024-09-10 22:05 ` Mark Brown
2024-09-10 23:30 ` Shuah Khan
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=2024091051-blooper-comply-47d3@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=allen.lkml@gmail.com \
--cc=broonie@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®