All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Borislav Petkov <bp@alien8.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 Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] EDAC: i10nm, skx: fix randconfig builds
Date: Wed, 6 Mar 2019 14:48:29 +0100	[thread overview]
Message-ID: <CAK8P3a2kSrTkTespcBGr6oYi8nvriS9pwtM2nQ7gCxVB+TzLog@mail.gmail.com> (raw)
In-Reply-To: <20190305143453.GC8256@zn.tnic>

[-- Attachment #1: Type: text/plain, Size: 577 bytes --]

On Tue, Mar 5, 2019 at 3:34 PM Borislav Petkov <bp@alien8.de> wrote:
>
> 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...

Quite possible, here is the fill .config file that I used as attachment

      Arnd

[-- Attachment #2: 0x8A152468-config.gz --]
[-- Type: application/gzip, Size: 30568 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: Borislav Petkov <bp@alien8.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 Mailing List <linux-kernel@vger.kernel.org>
Subject: EDAC: i10nm, skx: fix randconfig builds
Date: Wed, 6 Mar 2019 14:48:29 +0100	[thread overview]
Message-ID: <CAK8P3a2kSrTkTespcBGr6oYi8nvriS9pwtM2nQ7gCxVB+TzLog@mail.gmail.com> (raw)

On Tue, Mar 5, 2019 at 3:34 PM Borislav Petkov <bp@alien8.de> wrote:
>
> 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...

Quite possible, here is the fill .config file that I used as attachment

      Arnd

  reply	other threads:[~2019-03-06 13:48 UTC|newest]

Thread overview: 44+ 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 13:21 ` Arnd Bergmann
2019-03-05 14:34 ` [PATCH] " Borislav Petkov
2019-03-05 14:34   ` Borislav Petkov
2019-03-06 13:48   ` Arnd Bergmann [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 17:58       ` Luck, Tony
2019-03-06 20:15       ` [PATCH] " Arnd Bergmann
2019-03-06 20:15         ` Arnd Bergmann
2019-03-13 23:01         ` [PATCH] " Luck, Tony
2019-03-13 23:01           ` Luck, Tony
2019-03-14  7:09           ` [PATCH] " Arnd Bergmann
2019-03-14  7:09             ` Arnd Bergmann
2019-03-14 11:04             ` [PATCH] " Borislav Petkov
2019-03-14 11:04               ` Borislav Petkov
2019-03-14 21:59               ` [PATCH] " Luck, Tony
2019-03-14 21:59                 ` Luck, Tony
2019-03-15  9:43                 ` [PATCH] " Borislav Petkov
2019-03-15  9:43                   ` Borislav Petkov
2019-03-15 15:57                   ` [PATCH] " Luck, Tony
2019-03-15 15:57                     ` Luck, Tony
2019-03-15 17:37                     ` [PATCH] " Borislav Petkov
2019-03-15 17:37                       ` Borislav Petkov
2019-03-15 17:49                       ` [PATCH] " Luck, Tony
2019-03-15 17:49                         ` Luck, Tony
2019-03-15 18:02                         ` [PATCH] " Borislav Petkov
2019-03-15 18:02                           ` Borislav Petkov
2019-03-15 18:11                           ` [PATCH] " Luck, Tony
2019-03-15 18:11                             ` Luck, Tony
2019-03-15 21:03                             ` [PATCH] " Arnd Bergmann
2019-03-15 21:03                               ` Arnd Bergmann
2019-03-15 21:28                               ` [PATCH] " Luck, Tony
2019-03-15 21:28                                 ` Luck, Tony
2019-03-22 14:00                                 ` [PATCH] " Arnd Bergmann
2019-03-22 14:00                                   ` Arnd Bergmann
2019-03-22 17:55                                   ` [PATCH] " Luck, Tony
2019-03-22 17:55                                     ` Luck, Tony
2019-03-22 19:56                                     ` [PATCH] " Arnd Bergmann
2019-03-22 19:56                                       ` Arnd Bergmann
2019-03-21 22:13                               ` [PATCH] " Luck, Tony
2019-03-21 22:13                                 ` Luck, Tony
2019-03-22 22:59                                 ` [PATCH] " Borislav Petkov
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=CAK8P3a2kSrTkTespcBGr6oYi8nvriS9pwtM2nQ7gCxVB+TzLog@mail.gmail.com \
    --to=arnd@arndb.de \
    --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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.