public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
	linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
	akpm@linux-foundation.org, 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,
	conor@kernel.org, hargar@microsoft.com, broonie@kernel.org
Subject: Re: [PATCH 6.12 000/223] 6.12.25-rc1 review
Date: Mon, 28 Apr 2025 13:36:58 +0200	[thread overview]
Message-ID: <2025042833-carefully-lapped-d05c@gregkh> (raw)
In-Reply-To: <de718b6b-cbe1-4ccd-be70-794b60e91e0b@roeck-us.net>

On Sat, Apr 26, 2025 at 07:33:51PM -0700, Guenter Roeck wrote:
> Hi Greg,
> 
> On 4/23/25 07:41, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 6.12.25 release.
> > There are 223 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, 25 Apr 2025 14:25:27 +0000.
> > Anything received after that time might be too late.
> > 
> ...
> > Nathan Chancellor <nathan@kernel.org>
> >      kbuild: Add '-fno-builtin-wcslen'
> > 
> 
> This patch was already in 6.12.24, and it is now twice in 6.12.y.
> 
> 3802df8552de kbuild: Add '-fno-builtin-wcslen'
> 9c03f6194e88 kbuild: Add '-fno-builtin-wcslen'
> 
> and
> 
> $ grep fno-builtin-wcslen Makefile
> KBUILD_CFLAGS += -fno-builtin-wcslen
> KBUILD_CFLAGS += -fno-builtin-wcslen
> 
> This is the second time this happened in the 6.12 series. The other sequence is
> 
> 61749c035911 Revert "vfio/platform: check the bounds of read/write syscalls"
> 61ba518195d6 vfio/platform: check the bounds of read/write syscalls
> a20fcaa230f7 vfio/platform: check the bounds of read/write syscalls
> 
> Would it be possible to avoid those duplicates ? It doesn't matter in
> the above cases, but we might not always be that lucky.

Sorry about that, it's not a normal thing, and yes, our scripts should
check it.  I'll work on adding it in the future, thanks.

greg k-h

      reply	other threads:[~2025-04-28 11:37 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-23 14:41 [PATCH 6.12 000/223] 6.12.25-rc1 review Greg Kroah-Hartman
2025-04-23 14:44 ` [PATCH 6.12 186/223] arm64/sysreg: Update register fields for ID_AA64MMFR0_EL1 Greg Kroah-Hartman
2025-04-23 14:44 ` [PATCH 6.12 187/223] arm64/sysreg: Add register fields for HDFGRTR2_EL2 Greg Kroah-Hartman
2025-04-23 14:44 ` [PATCH 6.12 188/223] arm64/sysreg: Add register fields for HDFGWTR2_EL2 Greg Kroah-Hartman
2025-04-23 14:44 ` [PATCH 6.12 189/223] arm64/sysreg: Add register fields for HFGITR2_EL2 Greg Kroah-Hartman
2025-04-23 14:44 ` [PATCH 6.12 190/223] arm64/sysreg: Add register fields for HFGRTR2_EL2 Greg Kroah-Hartman
2025-04-23 14:44 ` [PATCH 6.12 191/223] arm64/sysreg: Add register fields for HFGWTR2_EL2 Greg Kroah-Hartman
2025-04-23 14:44 ` [PATCH 6.12 192/223] arm64/boot: Enable EL2 requirements for FEAT_PMUv3p9 Greg Kroah-Hartman
2025-04-23 19:36 ` [PATCH 6.12 000/223] 6.12.25-rc1 review Peter Schneider
2025-04-23 21:14 ` Shuah Khan
2025-04-23 23:53 ` Mark Brown
2025-04-24  7:15 ` Ron Economos
2025-04-24  7:34 ` Naresh Kamboju
2025-04-24 10:54 ` Jon Hunter
2025-04-24 13:14 ` Florian Fainelli
2025-04-24 17:58 ` Markus Reichelt
2025-04-25  0:14 ` Miguel Ojeda
2025-04-27  2:33 ` Guenter Roeck
2025-04-28 11:36   ` Greg Kroah-Hartman [this message]

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=2025042833-carefully-lapped-d05c@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