From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: <balbi@ti.com>, linux-kernel <linux-kernel@vger.kernel.org>,
<linux-kbuild@vger.kernel.org>
Subject: Re: Kconfig "softdepends" idea
Date: Tue, 30 Apr 2013 15:01:09 +0300 [thread overview]
Message-ID: <517FB285.7030903@ti.com> (raw)
In-Reply-To: <20130430114004.GA15804@merkur.ravnborg.org>
[-- Attachment #1: Type: text/plain, Size: 1467 bytes --]
On 04/30/2013 02:40 PM, Sam Ravnborg wrote:
>> SHOW_ALL_DRIVERS" is not very descriptive. I'm not sure if that matters,
>> though. One doesn't need to read the Kconfig files every day =).
>>
>> But presuming most of the drivers would use that, it would add quite a
>> bit of repetition to the Kconfig files. Well, ok, I have no idea how
>> many drivers have dependencies that could be removed.
>>
>> So SHOW_ALL_DRIVERS sounds quite an easy solution to this.
>
> Someone suggested to add symbols that are only set yo "y" for allyesconfig or allmodconfig.
> This would be what you actuayl require here as what you are after is better
> build coverage.
Sorry, I didn't quite get this. Do you mean that if I do allyesconfig,
SHOW_ALL_DRIVERS would get enabled, but not otherwise?
> But we should not annouyt the user just to get better build coverage - which
> is why hiding irrelevant symbols is good.
No disagreement there.
But I must say good build coverage is also important (I broke a powerpc
fb driver compilation with my mmap changes, and after fixing the
compilation I introduced a warning...). So I think it's a worthy goal to
have most of the drivers arch-independent, and make it possible to build
them if the user so wants.
I'll do a bit experimenting with fb drivers to see how the
SHOW_ALL_DRIVERS would work. And if there are any other fb drivers than
omapfb that actually can be compiled on other archs.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]
next prev parent reply other threads:[~2013-04-30 12:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-30 9:52 Kconfig "softdepends" idea Tomi Valkeinen
2013-04-30 10:24 ` Sam Ravnborg
2013-04-30 10:33 ` Felipe Balbi
2013-04-30 11:10 ` Tomi Valkeinen
2013-04-30 11:40 ` Sam Ravnborg
2013-04-30 12:01 ` Tomi Valkeinen [this message]
2013-04-30 11:36 ` Sam Ravnborg
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=517FB285.7030903@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=balbi@ti.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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