From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: linux-stable <stable@vger.kernel.org>,
Sasha Levin <sashal@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@somainline.org>,
Stephan Gerhold <stephan@gerhold.net>,
Stephen Boyd <swboyd@chromium.org>,
lkft-triage@lists.linaro.org
Subject: Re: qcom :apq8016-sbc.dtsi:412.21-414.5: ERROR (duplicate_label): /soc/codec: Duplicate label 'lpass_codec' on /soc/codec and /soc@0/codec
Date: Wed, 24 Nov 2021 17:15:46 +0100 [thread overview]
Message-ID: <YZ5lMnv8rTEturEp@kroah.com> (raw)
In-Reply-To: <CA+G9fYsa=04=sKsxH2=5yh3NqGTZUpcD-4OiKcfiFGSH3DP+FQ@mail.gmail.com>
On Wed, Nov 24, 2021 at 05:48:14PM +0530, Naresh Kamboju wrote:
> Hi Greg,
>
> On Wed, 24 Nov 2021 at 16:52, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> >
> > On Wed, Nov 24, 2021 at 03:30:09PM +0530, Naresh Kamboju wrote:
> > > Regression found on arm64 gcc-11 builds
> > > Following build warnings / errors reported on stable-rc 5.4.
> > >
> > > metadata:
> > > git_describe: v5.4.161-99-g60345e6d23ca
> > > git_repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
> > > git_short_log: 60345e6d23ca (\"Linux 5.4.162-rc1\")
> > > target_arch: arm64
> > > toolchain: gcc-11
> > >
> > > build error :
> > > --------------
> > > builds/linux/arch/arm64/boot/dts/qcom/apq8016-sbc.dtsi:412.21-414.5:
> > > ERROR (duplicate_label): /soc/codec: Duplicate label 'lpass_codec' on
> > > /soc/codec and /soc@0/codec
> > > ERROR: Input tree has errors, aborting (use -f to force output)
> > > make[3]: *** [scripts/Makefile.lib:285:
> > > arch/arm64/boot/dts/qcom/apq8016-sbc.dtb] Error 2
>
> > I can not figure out what commit caused this problem. Any pointers
> > would be appreciated...
>
> The bisect tool pointed to,
>
> b979ffa8bbd6e4c33df7f3e7ac3d63f2234c023c is the first bad commit
> commit b979ffa8bbd6e4c33df7f3e7ac3d63f2234c023c
> Author: Stephan Gerhold <stephan@gerhold.net>
> Date: Tue Sep 21 17:21:18 2021 +0200
>
> arm64: dts: qcom: msm8916: Add unit name for /soc node
>
> [ Upstream commit 7a62bfebc8c94bdb6eb8f54f49889dc6b5b79601 ]
>
> This fixes the following warning when building with W=1:
> Warning (unit_address_vs_reg): /soc: node has a reg or ranges property,
> but no unit name
>
> Signed-off-by: Stephan Gerhold <stephan@gerhold.net>
> Reviewed-by: Stephen Boyd <swboyd@chromium.org>
> Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
> Link: https://lore.kernel.org/r/20210921152120.6710-1-stephan@gerhold.net
> Signed-off-by: Sasha Levin <sashal@kernel.org>
>
> arch/arm64/boot/dts/qcom/msm8916.dtsi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Now dropped from everywhere, thanks.
greg k-h
prev parent reply other threads:[~2021-11-24 16:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-24 10:00 qcom :apq8016-sbc.dtsi:412.21-414.5: ERROR (duplicate_label): /soc/codec: Duplicate label 'lpass_codec' on /soc/codec and /soc@0/codec Naresh Kamboju
2021-11-24 11:22 ` Greg Kroah-Hartman
2021-11-24 12:18 ` Naresh Kamboju
2021-11-24 16:15 ` 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=YZ5lMnv8rTEturEp@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=angelogioacchino.delregno@somainline.org \
--cc=bjorn.andersson@linaro.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=stephan@gerhold.net \
--cc=swboyd@chromium.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