All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
Cc: Peter Schneider <pschneider1968@googlemail.com>,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	gregkh@linuxfoundation.org, patches@lists.linux.dev,
	torvalds@linux-foundation.org, akpm@linux-foundation.org,
	linux@roeck-us.net, shuah@kernel.org, patches@kernelci.org,
	lkft-triage@lists.linaro.org, pavel@nabladev.com,
	jonathanh@nvidia.com, f.fainelli@gmail.com,
	sudipm.mukherjee@gmail.com, rwarsow@gmx.de, conor@kernel.org,
	hargar@microsoft.com, broonie@kernel.org, achill@achill.org,
	sr@sladewatkins.com
Subject: Re: [PATCH 6.1 000/533] 6.1.165-rc2 review
Date: Mon, 2 Mar 2026 13:07:47 -0500	[thread overview]
Message-ID: <aaXR88OfyuzhWaqw@laps> (raw)
In-Reply-To: <06e95a5d-70c7-430a-8caf-7af0da26bcf1@oracle.com>

On Mon, Mar 02, 2026 at 11:28:18PM +0530, Harshit Mogalapalli wrote:
>Hi Sasha,
>
>>>Also I see something unusual -->
>>>
>>>6.1.165-rc1 --> 232 patches.
>>>
>>>6.1.165-rc2 --> 533 patches.
>>>
>>>Can you please check ?
>>
>>That's the reason for -rc2 :) See:
>>
>>https://lore.kernel.org/all/aaWWE5uQqz_eG69i@laps/
>
>Thanks, but shouldn't the 533 - 232 = 301 patches be sent to stable 
>mailing list ?
>
>Also not speaking about 6.1.y, but when rc1 passes tests, I don't 
>trigger tests for rc2. Should I always retrigger tests for 6.12.X-rc2 
>?
>
>Usually rc1 --> rc2 --> its mostly 2-5 patches in general.

Yup, this one ended up being a bit bigger :)

I didn't send out the whole batch of mails, but it's indeed a larger update.

-- 
Thanks,
Sasha

  reply	other threads:[~2026-03-02 18:08 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-02 16:09 [PATCH 6.1 000/533] 6.1.165-rc2 review Sasha Levin
2026-03-02 17:26 ` Peter Schneider
2026-03-02 17:36   ` Harshit Mogalapalli
2026-03-02 17:49     ` Sasha Levin
2026-03-02 17:58       ` Harshit Mogalapalli
2026-03-02 18:07         ` Sasha Levin [this message]
2026-03-02 17:48   ` Sasha Levin
2026-03-02 17:57     ` Peter Schneider
2026-03-02 18:09       ` Sasha Levin
2026-03-02 18:15         ` Peter Schneider
2026-03-02 19:46       ` Brett A C Sheffield
2026-03-02 20:12         ` Peter Schneider
2026-03-02 19:35 ` Brett A C Sheffield
2026-03-02 19:55 ` Peter Schneider
2026-03-03  4:52 ` Florian Fainelli
2026-03-03  7:34 ` Francesco Dolcini
2026-03-03 12:26 ` Ron Economos
2026-03-03 14:12 ` Jon Hunter
2026-03-03 19:37 ` Mark Brown
2026-03-03 21:18 ` Miguel Ojeda
2026-03-04  6:14 ` Hardik Garg
2026-03-04 17:47 ` 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=aaXR88OfyuzhWaqw@laps \
    --to=sashal@kernel.org \
    --cc=achill@achill.org \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=conor@kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hargar@microsoft.com \
    --cc=harshit.m.mogalapalli@oracle.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@nabladev.com \
    --cc=pschneider1968@googlemail.com \
    --cc=rwarsow@gmx.de \
    --cc=shuah@kernel.org \
    --cc=sr@sladewatkins.com \
    --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.