From: Borislav Petkov <bp@alien8.de>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
James Morse <james.morse@arm.com>,
Qiuxu Zhuo <qiuxu.zhuo@intel.com>,
Tony Luck <tony.luck@intel.com>,
linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] EDAC: i10nm, skx: fix randconfig builds
Date: Tue, 5 Mar 2019 15:34:53 +0100 [thread overview]
Message-ID: <20190305143453.GC8256@zn.tnic> (raw)
In-Reply-To: <20190305132147.3739133-1-arnd@arndb.de>
On Tue, Mar 05, 2019 at 02:21:30PM +0100, Arnd Bergmann wrote:
> In a configuration where one of the two drivers is built-in and the
> other one is a module, kbuild tries to add the modular file into
> vmlinux, and fails with
There must be something more to that .config of yours because both
CONFIG_EDAC_SKX=m
CONFIG_EDAC_I10NM=y
and
CONFIG_EDAC_SKX=y
CONFIG_EDAC_I10NM=m
work ok here...
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2019-03-05 14:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-05 13:21 [PATCH] EDAC: i10nm, skx: fix randconfig builds Arnd Bergmann
2019-03-05 14:34 ` Borislav Petkov [this message]
2019-03-06 13:48 ` Arnd Bergmann
2019-03-06 17:58 ` [PATCH] EDAC, {skx|i10nm}_edac: Fix randconfig build error Luck, Tony
2019-03-06 20:15 ` Arnd Bergmann
2019-03-13 23:01 ` Luck, Tony
2019-03-14 7:09 ` Arnd Bergmann
2019-03-14 11:04 ` Borislav Petkov
2019-03-14 21:59 ` Luck, Tony
2019-03-15 9:43 ` Borislav Petkov
2019-03-15 15:57 ` Luck, Tony
2019-03-15 17:37 ` Borislav Petkov
2019-03-15 17:49 ` Luck, Tony
2019-03-15 18:02 ` Borislav Petkov
2019-03-15 18:11 ` Luck, Tony
2019-03-15 21:03 ` Arnd Bergmann
2019-03-15 21:28 ` Luck, Tony
2019-03-22 14:00 ` Arnd Bergmann
2019-03-22 17:55 ` Luck, Tony
2019-03-22 19:56 ` Arnd Bergmann
2019-03-21 22:13 ` Luck, Tony
2019-03-22 22:59 ` 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=20190305143453.GC8256@zn.tnic \
--to=bp@alien8.de \
--cc=arnd@arndb.de \
--cc=james.morse@arm.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=qiuxu.zhuo@intel.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