From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Ron Economos <re@w6rz.net>
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,
pavel@denx.de, 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
Subject: Re: [PATCH 6.17 000/371] 6.17.4-rc1 review
Date: Sun, 19 Oct 2025 14:02:32 +0200 [thread overview]
Message-ID: <2025101933-utensil-campfire-75f8@gregkh> (raw)
In-Reply-To: <90bc04ea-e7ec-49b9-ae6e-d0e2c85bbf96@w6rz.net>
On Fri, Oct 17, 2025 at 04:04:23PM -0700, Ron Economos wrote:
> On 10/17/25 07:49, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 6.17.4 release.
> > There are 371 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 Sun, 19 Oct 2025 14:50:59 +0000.
> > Anything received after that time might be too late.
> >
> > The whole patch series can be found in one patch at:
> > https://www.kernel.org/pub/linux/kernel/v6.x/stable-review/patch-6.17.4-rc1.gz
> > or in the git tree and branch at:
> > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.17.y
> > and the diffstat can be found below.
> >
> > thanks,
> >
> > greg k-h
>
> Build fails for RISC-V with:
>
> In file included from ./include/linux/pgtable.h:6,
> from ./include/linux/mm.h:31,
> from arch/riscv/kernel/asm-offsets.c:8:
> ./arch/riscv/include/asm/pgtable.h:963:21: error: redefinition of
> 'pudp_huge_get_and_clear'
> 963 | static inline pud_t pudp_huge_get_and_clear(struct mm_struct *mm,
> | ^~~~~~~~~~~~~~~~~~~~~~~
> ./arch/riscv/include/asm/pgtable.h:946:21: note: previous definition of
> 'pudp_huge_get_and_clear' with type 'pud_t(struct mm_struct *, long unsigned
> int, pud_t *)'
> 946 | static inline pud_t pudp_huge_get_and_clear(struct mm_struct *mm,
> | ^~~~~~~~~~~~~~~~~~~~~~~
>
> Reverting 06536c4857271eeb19d76dbb4af989e2654a94e0 riscv: use an atomic xchg
> in pudp_huge_get_and_clear() fixes the build.
>
> The problem is that this patch was already applied to 6.17 just before
> release, so the function pudp_huge_get_and_clear() ends up being duplicated
> in the file.
Thanks, I'll go drop this patch now, thanks.
greg k-h
next prev parent reply other threads:[~2025-10-19 12:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-17 14:49 [PATCH 6.17 000/371] 6.17.4-rc1 review Greg Kroah-Hartman
2025-10-17 14:51 ` [PATCH 6.17 094/371] tools build: Align warning options with perf Greg Kroah-Hartman
2025-10-17 14:51 ` [PATCH 6.17 095/371] perf python: split Clang options when invoking Popen Greg Kroah-Hartman
2025-10-17 18:18 ` [PATCH 6.17 000/371] 6.17.4-rc1 review Ronald Warsow
2025-10-17 18:21 ` Jon Hunter
2025-10-17 21:47 ` Hardik Garg
2025-10-17 23:04 ` Ron Economos
2025-10-19 12:02 ` Greg Kroah-Hartman [this message]
2025-10-18 0:24 ` Shuah Khan
2025-10-18 3:45 ` Florian Fainelli
2025-10-18 3:53 ` Peter Schneider
2025-10-18 7:52 ` Brett A C Sheffield
2025-10-18 9:18 ` Dileep malepu
2025-10-18 10:17 ` Markus Reichelt
2025-10-18 16:19 ` Miguel Ojeda
2025-10-19 10:36 ` Pascal Ernster
2025-10-20 8:35 ` 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=2025101933-utensil-campfire-75f8@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=achill@achill.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=re@w6rz.net \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--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