From: Borislav Petkov <bp@alien8.de>
To: Robert Richter <rric@kernel.org>
Cc: Rob Herring <robherring2@gmail.com>,
linux-kernel@vger.kernel.org,
Rob Herring <rob.herring@calxeda.com>,
Doug Thompson <dougthompson@xmission.com>,
linux-edac@vger.kernel.org
Subject: Re: [PATCH] edac, highbank: remove dependency on ARCH_HIGHBANK
Date: Fri, 8 Nov 2013 15:47:21 +0100 [thread overview]
Message-ID: <20131108144700.GB7044@x1.alien8.de> (raw)
In-Reply-To: <20131108135918.GO7429@rric.localhost>
On Fri, Nov 08, 2013 at 02:59:18PM +0100, Robert Richter wrote:
> Can't we just take
>
> depends on EDAC_MM_EDAC && (ARCH_MULTI_V7 || ARM64)
>
> as a first step to increase build coverage?
Yep, that's basically what I was suggesting.
> There is also COMPILE_TEST that could be used which is exactly what we
> want here: "Compile also drivers which will not load":
>
> depends on EDAC_MM_EDAC && (ARCH_MULTI_V7 || ARM64 || COMPILE_TEST)
>
> This should enable it with allmodconfig.
You could do this but the first is already coverage enough IMO and, as I
said previously, compiling this thing on other architectures could raise
bugs/issues which are not necessarily such on arm/arm64, for example.
--
Regards/Gruss,
Boris.
next prev parent reply other threads:[~2013-11-08 14:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-06 3:25 Rob Herring
2013-11-06 14:20 ` Borislav Petkov
2013-11-06 16:15 ` Rob Herring
2013-11-06 16:54 ` Borislav Petkov
2013-11-06 17:17 ` Rob Herring
2013-11-07 12:27 ` Borislav Petkov
2013-11-07 13:23 ` Rob Herring
2013-11-07 13:33 ` Borislav Petkov
2013-11-08 13:59 ` Robert Richter
2013-11-08 14:47 ` Borislav Petkov [this message]
2013-11-11 10:29 ` Robert Richter
2013-11-11 10:47 ` Borislav Petkov
2013-11-11 11:09 ` Robert Richter
2013-11-11 15:06 ` Rob Herring
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=20131108144700.GB7044@x1.alien8.de \
--to=bp@alien8.de \
--cc=dougthompson@xmission.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rob.herring@calxeda.com \
--cc=robherring2@gmail.com \
--cc=rric@kernel.org \
/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®