From: Sasha Levin <sashal@kernel.org>
To: "Daniel Díaz" <daniel.diaz@linaro.org>
Cc: linux-kernel@vger.kernel.org, stable@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, florian.fainelli@broadcom.com,
pavel@denx.de
Subject: Re: [PATCH 6.8 000/710] 6.8.2-rc2 review
Date: Mon, 25 Mar 2024 19:50:59 -0400 [thread overview]
Message-ID: <ZgIN4zldW-htJ3lk@sashalap> (raw)
In-Reply-To: <CAEUSe79J7w3=oRAkTks80HLR9CbbkzGXTnubOuzmBYpZBnnttQ@mail.gmail.com>
On Mon, Mar 25, 2024 at 09:18:03AM -0600, Daniel Díaz wrote:
>Hello!
>
>On Mon, 25 Mar 2024 at 06:00, Sasha Levin <sashal@kernel.org> wrote:
>> This is the start of the stable review cycle for the 6.8.2 release.
>> There are 710 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.
>
>A newer revision was pushed on to the linux-6.8.y branch a couple of
>hours later (f44e3394ca9c) with 707 patches. Is that on its way to
>become RC3 or is that Git SHA superseding the previous revision
>(eed20d88c6a6)?
Yes, superseding please - I dropped 3 of the bpf patches.
--
Thanks,
Sasha
next prev parent reply other threads:[~2024-03-25 23:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 12:00 [PATCH 6.8 000/710] 6.8.2-rc2 review Sasha Levin
2024-03-25 15:18 ` Daniel Díaz
2024-03-25 23:50 ` Sasha Levin [this message]
2024-03-25 17:56 ` SeongJae Park
2024-03-25 18:14 ` Naresh Kamboju
2024-03-25 20:13 ` Justin Forbes
2024-03-25 21:29 ` Florian Fainelli
2024-03-26 3:45 ` Bagas Sanjaya
2024-03-26 9:00 ` Ron Economos
2024-03-26 11:19 ` Jiri Slaby
2024-03-26 15:27 ` Daniel Díaz
2024-03-26 16:31 ` Shuah Khan
2024-03-26 21:34 ` Shreeya Patel
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=ZgIN4zldW-htJ3lk@sashalap \
--to=sashal@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=daniel.diaz@linaro.org \
--cc=florian.fainelli@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=pavel@denx.de \
--cc=shuah@kernel.org \
--cc=stable@vger.kernel.org \
--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