netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michal Simek <monstr@monstr.eu>
To: Mark Brown <broonie@kernel.org>
Cc: Jean Delvare <jdelvare@suse.de>,
	netdev@vger.kernel.org, Nicolas Ferre <nicolas.ferre@atmel.com>,
	Grant Likely <grant.likely@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Fengguang Wu <fengguang.wu@intel.com>
Subject: Re: [PATCH v2] net: cadence: Add architecture dependencies
Date: Wed, 23 Apr 2014 15:16:04 +0200	[thread overview]
Message-ID: <5357BD14.1000608@monstr.eu> (raw)
In-Reply-To: <20140423113402.GV12304@sirena.org.uk>

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

On 04/23/2014 01:34 PM, Mark Brown wrote:
> On Wed, Apr 23, 2014 at 01:14:41PM +0200, Michal Simek wrote:
>> On 04/23/2014 12:48 PM, Jean Delvare wrote:
> 
>>> Originally I wanted to hide the Cadence drivers from X86 kernel
>>> configuration. If there's still a way to achieve that, let's do it. If
>>> not, we can leave the hardware dependency for ARM_AT91_ETHER and drop
>>> the one for MACB (and subsequently NET_CADENCE.) That's still better
>>> than nothing.
> 
>> Any reason to hide this driver for x86?
> 
> Distro maintainers like Jean are complaining about build times for their
> kernels if they enable absolutely everything so if they're never likely
> to see any hardware using something they want to skip it.

Is there any reasonable solution for this?
1. One group is saying use COMPILE_TEST for every driver to have better
coverage.
2. Next group is saying I don't want to build everything for my arch.

Fixing Kconfig to say !x86 is probably not the right way to go.

Isn't it enough not to enable absolutely everything?

Thanks,
Michal

-- 
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]

  reply	other threads:[~2014-04-23 13:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-14 13:38 [PATCH v2] net: cadence: Add architecture dependencies Jean Delvare
2014-04-15  4:08 ` David Miller
2014-04-22 20:32 ` Mark Brown
2014-04-23  7:16   ` Michal Simek
2014-04-23  7:40     ` Jean Delvare
2014-04-23  9:35       ` Michal Simek
2014-04-23 10:48         ` Jean Delvare
2014-04-23 11:14           ` Michal Simek
2014-04-23 11:34             ` Mark Brown
2014-04-23 13:16               ` Michal Simek [this message]
2014-04-23 13:27                 ` Jean Delvare
2014-04-23 14:23                 ` Mark Brown
2014-04-23 11:27           ` Mark Brown
2014-04-23 10:04       ` Mark Brown

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=5357BD14.1000608@monstr.eu \
    --to=monstr@monstr.eu \
    --cc=broonie@kernel.org \
    --cc=fengguang.wu@intel.com \
    --cc=grant.likely@linaro.org \
    --cc=jdelvare@suse.de \
    --cc=netdev@vger.kernel.org \
    --cc=nicolas.ferre@atmel.com \
    --cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).