From: "Arnd Bergmann" <arnd@arndb.de>
To: "Geert Uytterhoeven" <geert@linux-m68k.org>
Cc: "Naresh Kamboju" <naresh.kamboju@linaro.org>,
"open list" <linux-kernel@vger.kernel.org>,
linux-next <linux-next@vger.kernel.org>,
lkft-triage@lists.linaro.org,
clang-built-linux <llvm@lists.linux.dev>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
"Linux ARM" <linux-arm-kernel@lists.infradead.org>,
Netdev <netdev@vger.kernel.org>,
"Nathan Chancellor" <nathan@kernel.org>,
"Nick Desaulniers" <ndesaulniers@google.com>,
"Anders Roxell" <anders.roxell@linaro.org>,
"Geert Uytterhoeven" <geert+renesas@glider.be>,
"David S . Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Maxime Coquelin" <mcoquelin.stm32@gmail.com>,
maxime.chevallier@bootlin.com,
"Simon Horman" <simon.horman@corigine.com>
Subject: Re: arm: shmobile_defconfig: ld.lld: error: undefined symbol: lynx_pcs_destroy
Date: Tue, 06 Jun 2023 12:34:43 +0200 [thread overview]
Message-ID: <34b7bbab-a301-42ad-a2cc-3b68ee1475b7@app.fastmail.com> (raw)
In-Reply-To: <CAMuHMdWKL3UHzkEq3qOChMsgOsr+9uj215x55xLzbOUJWwQVzg@mail.gmail.com>
On Tue, Jun 6, 2023, at 12:31, Geert Uytterhoeven wrote:
> On Tue, Jun 6, 2023 at 12:21 PM Arnd Bergmann <arnd@arndb.de> wrote:
>> On Tue, Jun 6, 2023, at 11:28, Geert Uytterhoeven wrote:
>> > On Tue, Jun 6, 2023 at 11:16 AM Arnd Bergmann <arnd@arndb.de> wrote:
>> >> On Tue, Jun 6, 2023, at 11:01, Geert Uytterhoeven wrote:
>> >>
>> >> This won't work when PCS_LYNX is a loadable module and
>> >> STMMAC is built-in. I think we should just select PCS_LYNX
>> >
>> > Oops, you're right, forgot about that case.
>> > What about using IS_REACHABLE() instead?
>> > No, that won't work either, as DWMAC_SOCFPGA can be modular,
>> > with STMMAC builtin.
>>
>> It would work because of the 'select PCS_LYNX' below DWMAC_SOCFPGA,
>
> That was my first thought, but it won't work, as DWMAC_SOCFPGA=m
> causes PCS_LYNX=m, while main STMMAC can still be builtin.
Right, got it now.
Arnd
next prev parent reply other threads:[~2023-06-06 10:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+G9fYv0a-XxXfG6bNuPZGT=fzjtEfRGEYwk3n6M1WhEHUPo9g@mail.gmail.com>
2023-06-06 8:53 ` arm: shmobile_defconfig: ld.lld: error: undefined symbol: lynx_pcs_destroy Naresh Kamboju
2023-06-06 9:01 ` Geert Uytterhoeven
2023-06-06 9:15 ` Arnd Bergmann
2023-06-06 9:28 ` Geert Uytterhoeven
2023-06-06 10:21 ` Arnd Bergmann
2023-06-06 10:31 ` Geert Uytterhoeven
2023-06-06 10:34 ` Arnd Bergmann [this message]
2023-06-07 13:27 ` Aithal, Srikanth
2023-06-07 13:41 ` Russell King (Oracle)
2023-06-07 13:59 ` Arnd Bergmann
2023-06-09 5:22 ` Aithal, Srikanth
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=34b7bbab-a301-42ad-a2cc-3b68ee1475b7@app.fastmail.com \
--to=arnd@arndb.de \
--cc=anders.roxell@linaro.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=llvm@lists.linux.dev \
--cc=maxime.chevallier@bootlin.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=naresh.kamboju@linaro.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=simon.horman@corigine.com \
/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).