From: Alexander Lobakin <aleksander.lobakin@intel.com>
To: Arnd Bergmann <arnd@kernel.org>
Cc: Jakub Kicinski <kuba@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
"Paolo Abeni" <pabeni@redhat.com>,
Siddharth Vadapalli <s-vadapalli@ti.com>,
"Ravi Gunasekaran" <r-gunasekaran@ti.com>,
Roger Quadros <rogerq@kernel.org>,
"MD Danish Anwar" <danishanwar@ti.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
Diogo Ivo <diogo.ivo@siemens.com>, Tanmay Patil <t-patil@ti.com>,
"Simon Horman" <horms@kernel.org>,
Ratheesh Kannoth <rkannoth@marvell.com>,
"Grygorii Strashko" <grygorii.strashko@ti.com>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-omap@vger.kernel.org>, <bpf@vger.kernel.org>
Subject: Re: [PATCH 1/2] [v2] net: ethernet: ti-cpsw: fix linking built-in code to modules
Date: Wed, 17 Apr 2024 13:49:35 +0200 [thread overview]
Message-ID: <8663692f-528f-4d68-8c35-136e5f1244dc@intel.com> (raw)
In-Reply-To: <20240417084400.3034104-1-arnd@kernel.org>
From: Arnd Bergmann <arnd@kernel.org>
Date: Wed, 17 Apr 2024 10:43:01 +0200
> From: Arnd Bergmann <arnd@arndb.de>
>
> There are six variants of the cpsw driver, sharing various parts of
> the code: davinci-emac, cpsw, cpsw-switchdev, netcp, netcp_ethss and
> am65-cpsw-nuss.
https://lore.kernel.org/all/20221119225650.1044591-10-alobakin@pm.me
:D
>
> I noticed that this means some files can be linked into more than
> one loadable module, or even part of vmlinux but also linked into
> a loadable module, both of which mess up assumptions of the build
> system.
Thanks,
Olek
next prev parent reply other threads:[~2024-04-17 11:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 8:43 [PATCH 1/2] [v2] net: ethernet: ti-cpsw: fix linking built-in code to modules Arnd Bergmann
2024-04-17 11:49 ` Alexander Lobakin [this message]
2024-04-17 12:07 ` Arnd Bergmann
2024-04-17 12:14 ` Arnd Bergmann
2024-04-18 13:34 ` Paolo Abeni
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=8663692f-528f-4d68-8c35-136e5f1244dc@intel.com \
--to=aleksander.lobakin@intel.com \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=danishanwar@ti.com \
--cc=davem@davemloft.net \
--cc=diogo.ivo@siemens.com \
--cc=edumazet@google.com \
--cc=grygorii.strashko@ti.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=r-gunasekaran@ti.com \
--cc=rkannoth@marvell.com \
--cc=rogerq@kernel.org \
--cc=s-vadapalli@ti.com \
--cc=t-patil@ti.com \
--cc=vigneshr@ti.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