From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: linux-stable <stable@vger.kernel.org>,
lkft-triage@lists.linaro.org, Sasha Levin <sashal@kernel.org>,
Dan Carpenter <dan.carpenter@linaro.org>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
Benjamin Copeland <benjamin.copeland@linaro.org>
Subject: Re: stable-rc: queue/6.6: drivers/ufs/host/ufs-qcom.c:1929:13: error: 'host' undeclared (first use in this function)
Date: Thu, 12 Dec 2024 15:33:01 +0100 [thread overview]
Message-ID: <2024121244-scanning-grimace-b554@gregkh> (raw)
In-Reply-To: <CA+G9fYvkiFZxYFV_jKYOgePNMJDjQHL+BVo8SUWNVS37=aR5ig@mail.gmail.com>
On Thu, Dec 12, 2024 at 06:58:12PM +0530, Naresh Kamboju wrote:
> The arm64 builds failed on Linux stable-rc queues/6.6 due to following build
> warnings / errors.
>
> arm64:
> * build/gcc-13-defconfig-lkftconfig
>
> First seen on Linux stable-rc queues/6.6
> Good: v6.6.65
> Bad: v6.6.65-348-g690f793e86f4
>
> Build log:
> -----------
> drivers/ufs/host/ufs-qcom.c: In function 'ufs_qcom_remove':
> drivers/ufs/host/ufs-qcom.c:1929:13: error: 'host' undeclared (first
> use in this function)
> 1929 | if (host->esi_enabled)
> | ^~~~
> drivers/ufs/host/ufs-qcom.c:1929:13: note: each undeclared identifier
> is reported only once for each function it appears in
> make[6]: *** [scripts/Makefile.build:243: drivers/ufs/host/ufs-qcom.o] Error 1
>
> the commit that causes this build regression is,
> scsi: ufs: qcom: Only free platform MSIs when ESI is enabled
> commit 64506b3d23a337e98a74b18dcb10c8619365f2bd upstream.
Odd, that backport is broken, sorry about that. I'll go remove it.
greg k-h
prev parent reply other threads:[~2024-12-12 14:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 13:28 stable-rc: queue/6.6: drivers/ufs/host/ufs-qcom.c:1929:13: error: 'host' undeclared (first use in this function) Naresh Kamboju
2024-12-12 14:33 ` 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=2024121244-scanning-grimace-b554@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=benjamin.copeland@linaro.org \
--cc=dan.carpenter@linaro.org \
--cc=lkft-triage@lists.linaro.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.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