From: Randy Dunlap <rdunlap@xenotime.net>
To: Micha? Miros?aw <mirq-linux@rere.qmqm.pl>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>, netdev@vger.kernel.org
Subject: Re: Driver build-testing (was: [PATCH] net: dm9000: Fix build)
Date: Mon, 18 Apr 2011 08:28:25 -0700 [thread overview]
Message-ID: <20110418082825.86a21574.rdunlap@xenotime.net> (raw)
In-Reply-To: <20110418151729.GA4721@rere.qmqm.pl>
On Mon, 18 Apr 2011 17:17:29 +0200 Micha? Miros?aw wrote:
> On Mon, Apr 18, 2011 at 07:55:08AM -0700, Randy Dunlap wrote:
> > On Mon, 18 Apr 2011 16:51:02 +0200 Micha? Miros?aw wrote:
> >
> > > On Mon, Apr 18, 2011 at 01:25:22PM +0100, Mark Brown wrote:
> > > > On Mon, Apr 18, 2011 at 01:12:03PM +0200, Micha? Miros?aw wrote:
> > > > > This brings the issue of build testing effectiveness. In current code
> > > > > there is no configuration that makes all drivers build. I would like
> > > > > to see something like 'make brokenconfig' that would allow most of
> > > > > the code to be built, and not necessarily working. Maybe someone has
> > > > > an idea how to implement that?
> > > > For the drivers that genuinely are rather platform specific this tends
> > > > to fail very badly as you need headers that only come along with the
> > > > architecture.
> > > >
> > > > In the case of DM9000 if it fails to build on your platform then the
> > > > driver is just buggy - looking at the Kconfig I rather suspect that the
> > > > dependency on architectures should just be removed.
> > > I wonder if allyesconfig/allmodconfig is supposed to include code that's
> > > known not to work for a particular architecture.
> > all*config just use whatever is in all of the various Kconfig* files.
> > If they say "depends on $somearch", then so be it. If not, then the
> > remaining dependencies are used.
>
> Yes, I know how it works. I just wonder if removing those dependencies so
> that all drivers (even if known not to work) are built on all*config
> is acceptable. Or maybe there should be a config like 'disable all drivers
> that are known to build but not to work on this arch'?
AFAIK, it's always the case that we prefer not to have
depends on $somearch
for drivers, but the reality is that lots of them do depend on $ARCH
for header files etc., so they are listed that way. There's not much
that we can do about that. I don't think that removing those dependencies
is acceptable. OTOH, it may be acceptable to enable CONFIG_BROKEN so that
the drivers that depend on BROKEN can try to be built.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2011-04-18 15:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-18 11:04 [PATCH] net: dm9000: Fix build Mark Brown
2011-04-18 11:12 ` Driver build-testing (was: [PATCH] net: dm9000: Fix build) Michał Mirosław
2011-04-18 12:25 ` Mark Brown
2011-04-18 14:51 ` Micha? Miros?aw
2011-04-18 14:55 ` Randy Dunlap
2011-04-18 15:17 ` Micha? Miros?aw
2011-04-18 15:28 ` Randy Dunlap [this message]
2011-04-18 16:07 ` Mark Brown
2011-04-18 21:23 ` Driver build-testing David Miller
2011-04-18 21:19 ` [PATCH] net: dm9000: Fix build David Miller
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=20110418082825.86a21574.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=mirq-linux@rere.qmqm.pl \
--cc=netdev@vger.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).