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.1 000/157] 6.1.136-rc2 review
Date: Mon, 5 May 2025 10:57:27 +0200 [thread overview]
Message-ID: <2025050510-headlamp-omega-56bd@gregkh> (raw)
In-Reply-To: <f978ec9a-b103-40af-b116-6a9238197110@roeck-us.net>
On Sat, May 03, 2025 at 06:03:53AM -0700, Guenter Roeck wrote:
> On 5/1/25 01:14, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 6.1.136 release.
> > There are 157 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 Sat, 03 May 2025 08:08:16 +0000.
> > Anything received after that time might be too late.
> >
>
> Building loongarch:defconfig ... failed
> --------------
> Error log:
> arch/loongarch/mm/hugetlbpage.c: In function 'huge_pte_offset':
> arch/loongarch/mm/hugetlbpage.c:50:25: error: implicit declaration of function 'pmdp_get'; did you mean 'ptep_get'? [-Werror=implicit-function-declaration]
> 50 | return pmd_none(pmdp_get(pmd)) ? NULL : (pte_t *) pmd;
> | ^~~~~~~~
> | ptep_get
> arch/loongarch/mm/hugetlbpage.c:50:25: error: incompatible type for argument 1 of 'pmd_none'
> 50 | return pmd_none(pmdp_get(pmd)) ? NULL : (pte_t *) pmd;
> | ^~~~~~~~~~~~~
> | |
> | int
> In file included from arch/loongarch/include/asm/uaccess.h:17,
> from include/linux/uaccess.h:11,
> from include/linux/sched/task.h:11,
> from include/linux/sched/signal.h:9,
> from include/linux/rcuwait.h:6,
> from include/linux/percpu-rwsem.h:7,
> from include/linux/fs.h:33,
> from arch/loongarch/mm/hugetlbpage.c:6:
> arch/loongarch/include/asm/pgtable.h:198:34: note: expected 'pmd_t' but argument is of type 'int'
> 198 | static inline int pmd_none(pmd_t pmd)
> | ~~~~~~^~~
> arch/loongarch/mm/hugetlbpage.c:51:1: error: control reaches end of non-void function [-Werror=return-type]
Thanks, a fix has now been posted, let me do a release with it now...
greg k-h
prev parent reply other threads:[~2025-05-05 8:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-01 8:14 [PATCH 6.1 000/157] 6.1.136-rc2 review Greg Kroah-Hartman
2025-05-01 11:07 ` Jon Hunter
2025-05-01 16:52 ` Miguel Ojeda
2025-05-01 17:59 ` Peter Schneider
2025-05-01 20:26 ` Mark Brown
2025-05-01 21:29 ` Hardik Garg
2025-05-02 3:00 ` Naresh Kamboju
2025-05-02 12:55 ` Florian Fainelli
2025-05-03 13:03 ` Guenter Roeck
2025-05-05 8:57 ` 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=2025050510-headlamp-omega-56bd@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