From: Greg KH <gregkh@linuxfoundation.org>
To: Wentao Guan <guanwentao@uniontech.com>
Cc: achill@achill.org, akpm@linux-foundation.org, broonie@kernel.org,
conor@kernel.org, f.fainelli@gmail.com, hargar@microsoft.com,
jonathanh@nvidia.com, linux-kernel@vger.kernel.org,
linux@roeck-us.net, lkft-triage@lists.linaro.org,
patches@kernelci.org, patches@lists.linux.dev,
pavel@nabladev.com, rwarsow@gmx.de, shuah@kernel.org,
sr@sladewatkins.com, stable@vger.kernel.org,
sudipm.mukherjee@gmail.com, torvalds@linux-foundation.org
Subject: Re: [PATCH 6.6 000/175] 6.6.144-rc1 review
Date: Fri, 3 Jul 2026 11:39:51 +0200 [thread overview]
Message-ID: <2026070341-asleep-hazing-15a6@gregkh> (raw)
In-Reply-To: <20260703080126.567705-1-guanwentao@uniontech.com>
On Fri, Jul 03, 2026 at 04:01:27PM +0800, Wentao Guan wrote:
> Hi,
>
> Build failed in loongarch arch, which resolve in link:
> https://lore.kernel.org/stable/20260703032401.857553-1-chenhuacai@loongson.cn/
> https://lore.kernel.org/stable/2026070318-monotone-mug-74d6@gregkh/
>
> arch/loongarch/kernel/smp.c: In function ‘stop_this_cpu’:
> arch/loongarch/kernel/smp.c:616:9: error: implicit declaration of function ‘rcutree_report_cpu_dead’; did you mean ‘rcutree_prepare_cpu’? [-Werror=implicit-function-declaration]
> 616 | rcutree_report_cpu_dead();
> | ^~~~~~~~~~~~~~~~~~~~~~~
> | rcutree_prepare_cpu
>
> Build tested in our x86,arm64,riscv config successfully without error.
Offending commit already dropped.
thans,
greg k-h
next prev parent reply other threads:[~2026-07-03 9:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 16:18 [PATCH 6.6 000/175] 6.6.144-rc1 review Greg Kroah-Hartman
2026-07-02 19:46 ` Brett A C Sheffield
2026-07-02 20:46 ` Peter Schneider
2026-07-02 23:49 ` Miguel Ojeda
2026-07-03 6:33 ` Ron Economos
2026-07-03 7:13 ` Shung-Hsi Yu
2026-07-03 7:40 ` Francesco Dolcini
2026-07-03 8:01 ` Wentao Guan
2026-07-03 9:39 ` Greg KH [this message]
2026-07-03 9:42 ` Pavel Machek
2026-07-03 13:43 ` Mark Brown
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=2026070341-asleep-hazing-15a6@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=guanwentao@uniontech.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@nabladev.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox