From: Jean Delvare <jdelvare@suse.de>
To: monstr@monstr.eu
Cc: Mark Brown <broonie@kernel.org>,
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:27:10 +0200 [thread overview]
Message-ID: <20140423152710.4e6b7b9c@endymion.delvare> (raw)
In-Reply-To: <5357BD14.1000608@monstr.eu>
Hi Michal,
On Wed, 23 Apr 2014 15:16:04 +0200, Michal Simek wrote:
> On 04/23/2014 01:34 PM, Mark Brown wrote:
> > On Wed, Apr 23, 2014 at 01:14:41PM +0200, Michal Simek wrote:
> >> 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.
Exactly. See this discussion thread for details:
https://lkml.org/lkml/2014/4/14/280
> Is there any reasonable solution for this?
> 1. One group is saying use COMPILE_TEST for every driver to have better
> coverage.
I think pretty much everyone agrees with this. The problem is that
COMPILE_TEST is relatively new so a lot of old drivers don't have it
yet, and developers and maintainers are not yet used to using it or
asking for it.
> 2. Next group is saying I don't want to build everything for my arch.
I don't understand what you mean here.
The idea is that distro maintainers or simple users don't set
COMPILE_TEST so they only see what is useful to them, while developers
set COMPILE_TEST to be able to build-test everything.
Before COMPILE_TEST was introduced, it wasn't possible to make everyone
happy. Now it is, so let's just do it.
> Fixing Kconfig to say !x86 is probably not the right way to go.
Definitely not. I did not even consider it as an acceptable workaround.
If we can't come up with reasonable dependencies for a given driver, we
can just leave it as is. There's plenty of easier drivers to work on :)
> Isn't it enough not to enable absolutely everything?
Everything that is visible requires everyone around to make a decision.
The more we can help them, the easier the process.
--
Jean Delvare
SUSE L3 Support
next prev parent reply other threads:[~2014-04-23 13:27 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
2014-04-23 13:27 ` Jean Delvare [this message]
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=20140423152710.4e6b7b9c@endymion.delvare \
--to=jdelvare@suse.de \
--cc=broonie@kernel.org \
--cc=fengguang.wu@intel.com \
--cc=grant.likely@linaro.org \
--cc=monstr@monstr.eu \
--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