From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Kishon Vijay Abraham I <kishon@kernel.org>,
Vinod Koul <vkoul@kernel.org>
Cc: Mrinmay Sarkar <quic_msarkar@quicinc.com>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure after merge of the phy-next tree
Date: Fri, 18 Aug 2023 15:40:44 +1000 [thread overview]
Message-ID: <20230818154044.33b443a1@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 898 bytes --]
Hi all,
After merging the phy-next tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/phy/qualcomm/phy-qcom-qmp-pcie.c:2378:38: error: redefinition of 'qmp_pcie_offsets_v5_20'
2378 | static const struct qmp_pcie_offsets qmp_pcie_offsets_v5_20 = {
| ^~~~~~~~~~~~~~~~~~~~~~
drivers/phy/qualcomm/phy-qcom-qmp-pcie.c:2357:38: note: previous definition of 'qmp_pcie_offsets_v5_20' with type 'const struct qmp_pcie_offsets'
2357 | static const struct qmp_pcie_offsets qmp_pcie_offsets_v5_20 = {
| ^~~~~~~~~~~~~~~~~~~~~~
Caused by commits
a05b6d5135ec ("phy: qcom-qmp-pcie: add support for sa8775p")
64adc0bf06ad ("phy: qcom-qmp-pcie: populate offsets configuration")
I have used the phy-next tree from next-20230817 for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-08-18 5:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 5:40 Stephen Rothwell [this message]
2023-08-22 14:00 ` linux-next: build failure after merge of the phy-next tree Vinod Koul
-- strict thread matches above, loose matches on Subject: below --
2023-02-13 2:55 Stephen Rothwell
2023-02-13 5:17 ` Vinod Koul
2022-07-07 5:39 Stephen Rothwell
2022-07-07 5:53 ` Vinod Koul
2021-12-24 3:03 Stephen Rothwell
2021-12-24 4:37 ` Vinod Koul
2021-12-15 13:49 broonie
2021-12-15 14:14 ` Marcel Ziswiler
2021-12-15 15:20 ` Vinod Koul
2020-12-01 6:07 Stephen Rothwell
2020-12-01 6:45 ` Sergio Paracuellos
2020-12-01 10:39 ` Vinod Koul
2020-11-17 2:40 Stephen Rothwell
2020-11-17 10:00 ` Vinod Koul
2020-11-18 2:56 ` Stephen Rothwell
2020-11-18 4:23 ` Vinod Koul
2019-08-27 5:50 Stephen Rothwell
2017-03-30 3:47 Stephen Rothwell
2017-03-30 5:39 ` Kishon Vijay Abraham I
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=20230818154044.33b443a1@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=dmitry.baryshkov@linaro.org \
--cc=kishon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=quic_msarkar@quicinc.com \
--cc=vkoul@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;
as well as URLs for NNTP newsgroup(s).