From: Rob Herring <robherring2@gmail.com>
To: Borislav Petkov <bp@alien8.de>
Cc: linux-kernel@vger.kernel.org,
Rob Herring <rob.herring@calxeda.com>,
Doug Thompson <dougthompson@xmission.com>,
Robert Richter <rric@kernel.org>,
linux-edac@vger.kernel.org
Subject: Re: [PATCH] edac, highbank: remove dependency on ARCH_HIGHBANK
Date: Wed, 06 Nov 2013 10:15:04 -0600 [thread overview]
Message-ID: <527A6B08.5020302@gmail.com> (raw)
In-Reply-To: <20131106142025.GB16072@x1.alien8.de>
On 11/06/2013 08:20 AM, Borislav Petkov wrote:
> On Tue, Nov 05, 2013 at 09:25:52PM -0600, Rob Herring wrote:
>> From: Rob Herring <rob.herring@calxeda.com>
>>
>> In order to enable on arm64 and improve the build coverage, remove the
>> dependency on ARCH_HIGHBANK.
>>
>> Signed-off-by: Rob Herring <rob.herring@calxeda.com>
>> Cc: Doug Thompson <dougthompson@xmission.com>
>> Cc: Robert Richter <rric@kernel.org>
>> Cc: linux-edac@vger.kernel.org
>> ---
>> drivers/edac/Kconfig | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/edac/Kconfig b/drivers/edac/Kconfig
>> index 878f090..fc8aaaf 100644
>> --- a/drivers/edac/Kconfig
>> +++ b/drivers/edac/Kconfig
>> @@ -328,14 +328,14 @@ config EDAC_TILE
>>
>> config EDAC_HIGHBANK_MC
>> tristate "Highbank Memory Controller"
>> - depends on EDAC_MM_EDAC && ARCH_HIGHBANK
>> + depends on EDAC_MM_EDAC
>
> Please, no, this'll get enabled on other arches where this driver is
> simply N/A. It should only depend on the ARM arches it supports.
Other maintainers disagree because it reduces build coverage. Having
done some cross arch clean-up, I have to agree with that position.
Iterating builds over different arches is bad enough, but iterating over
all configs for each arch is a pain. It would be nice to have a uniform
policy here.
Rob
next prev parent reply other threads:[~2013-11-06 16:15 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 [this message]
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
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=527A6B08.5020302@gmail.com \
--to=robherring2@gmail.com \
--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=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