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, srw@sladewatkins.net, rwarsow@gmx.de,
conor@kernel.org
Subject: Re: [PATCH 6.5 000/112] 6.5.10-rc1 review
Date: Wed, 1 Nov 2023 12:28:12 +0100 [thread overview]
Message-ID: <2023110142-crimp-varied-fe90@gregkh> (raw)
In-Reply-To: <38fbd463-1160-0212-b9d2-6efeaaa6548e@w6rz.net>
On Tue, Oct 31, 2023 at 03:51:39PM -0700, Ron Economos wrote:
> On 10/31/23 10:00 AM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 6.5.10 release.
> > There are 112 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 Thu, 02 Nov 2023 16:58:38 +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.5.10-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.5.y
> > and the diffstat can be found below.
> >
> > thanks,
> >
> > greg k-h
>
> The build fails on RISC-V.
>
> arch/riscv/mm/hugetlbpage.c: In function ‘set_huge_pte_at’:
> arch/riscv/mm/hugetlbpage.c:188:13: error: ‘sz’ undeclared (first use in
> this function); did you mean ‘s8’?
> 188 | if (sz >= PGDIR_SIZE)
> | ^~
> | s8
> arch/riscv/mm/hugetlbpage.c:188:13: note: each undeclared identifier is
> reported only once for each function it appears in
>
> Caused by commit 16b6f77970f7a690c61de142511c9ac488d83e04
>
> riscv: fix set_huge_pte_at() for NAPOT mappings when a swap entry is set
>
> This patch requires mainline commit 62ba41d2761206664a1fdc998051324457da2dd6
>
> mm: riscv: fix an unsafe pte read in huge_pte_alloc()
Thanks, I'll just drop this commit and wait for someone who cares about
riscv, and 6.5.y (it's only going to be alive for another few weeks), to
resend the needed changes.
greg k-h
next prev parent reply other threads:[~2023-11-01 11:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 17:00 [PATCH 6.5 000/112] 6.5.10-rc1 review Greg Kroah-Hartman
2023-10-31 22:51 ` Ron Economos
2023-11-01 7:43 ` Naresh Kamboju
2023-11-01 11:28 ` Greg Kroah-Hartman [this message]
2023-10-31 23:24 ` Florian Fainelli
2023-11-01 0:12 ` Shuah Khan
2023-11-01 2:28 ` Justin Forbes
2023-11-01 2:55 ` Bagas Sanjaya
2023-11-01 10:08 ` Jon Hunter
2023-11-01 11:42 ` Ricardo B. Marliere
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=2023110142-crimp-varied-fe90@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.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=re@w6rz.net \
--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