From: "Arnd Bergmann" <arnd@arndb.de>
To: "Borislav Petkov" <bp@alien8.de>, "Arnd Bergmann" <arnd@kernel.org>
Cc: "Tony Luck" <tony.luck@intel.com>,
"Zhuo, Qiuxu" <qiuxu.zhuo@intel.com>,
"James Morse" <james.morse@arm.com>,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
"Robert Richter" <rric@kernel.org>,
"Marvin Lin" <milkfafa@gmail.com>,
"Shubhrajyoti Datta" <shubhrajyoti.datta@amd.com>,
"Sai Krishna Potthuri" <sai.krishna.potthuri@amd.com>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] EDAC, i10nm: make skx_common.o a separate module
Date: Wed, 29 May 2024 21:55:04 +0200 [thread overview]
Message-ID: <fc7f2a95-2a61-4eea-a1b8-b764893eabe3@app.fastmail.com> (raw)
In-Reply-To: <20240529193127.GEZleCjwyUtnDv_Nc0@fat_crate.local>
On Wed, May 29, 2024, at 21:31, Borislav Petkov wrote:
> On Wed, May 29, 2024 at 11:51:11AM +0200, Arnd Bergmann wrote:
>> From: Arnd Bergmann <arnd@arndb.de>
>>
>> Linking an object file into multiple modules causes a warning:
>>
>> scripts/Makefile.build:236: drivers/edac/Makefile: skx_common.o is added to multiple modules: i10nm_edac skx_edac
>
> What changed?
>
> This wasn't an issue until now-ish...
It has caused problems in enough other drivers that we now
have a warning for it, it was added in commit 598afa050403
("kbuild: warn objects shared among multiple modules").
Most modules are modified already, and we are now down to
the last handful. Since the bugs are fairly hard to understand
when they happen, it would be nice to enable the warning
by default.
Arnd
next prev parent reply other threads:[~2024-05-29 19:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-29 9:51 Arnd Bergmann
2024-05-29 16:14 ` Luck, Tony
2024-05-29 16:21 ` Arnd Bergmann
2024-05-29 18:27 ` Luck, Tony
2024-06-03 13:02 ` Zhuo, Qiuxu
2024-05-29 19:31 ` Borislav Petkov
2024-05-29 19:55 ` Arnd Bergmann [this message]
2024-05-29 20:09 ` Borislav Petkov
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=fc7f2a95-2a61-4eea-a1b8-b764893eabe3@app.fastmail.com \
--to=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=bp@alien8.de \
--cc=james.morse@arm.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=milkfafa@gmail.com \
--cc=qiuxu.zhuo@intel.com \
--cc=rric@kernel.org \
--cc=sai.krishna.potthuri@amd.com \
--cc=shubhrajyoti.datta@amd.com \
--cc=tony.luck@intel.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
all inboxes | Powered by JetHome®