From: Robert Richter <rric@kernel.org>
To: Borislav Petkov <bp@alien8.de>
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 14:59:18 +0100 [thread overview]
Message-ID: <20131108135918.GO7429@rric.localhost> (raw)
In-Reply-To: <20131107133329.GJ27116@x1.alien8.de>
On 07.11.13 14:33:29, Borislav Petkov wrote:
> On Thu, Nov 07, 2013 at 07:23:10AM -0600, Rob Herring wrote:
> > See, we are benefiting already.
>
> You can catch this when building on arm64, i.e. basically one of the
> target architectures for which the driver is meant for.
Can't we just take
depends on EDAC_MM_EDAC && (ARCH_MULTI_V7 || ARM64)
as a first step to increase build coverage?
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.
-Robert
next prev parent reply other threads:[~2013-11-08 13:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-06 3:25 [PATCH] edac, highbank: remove dependency on ARCH_HIGHBANK 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 [this message]
2013-11-08 14:47 ` Borislav Petkov
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=20131108135918.GO7429@rric.localhost \
--to=rric@kernel.org \
--cc=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 \
/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.