From: Adrian Bunk <bunk@kernel.org>
To: Jeff Garzik <jeff@garzik.org>
Cc: akpm@linux-foundation.org, netdev@vger.kernel.org,
randy.dunlap@oracle.com, auke-jan.h.kok@intel.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [patch 01/10] e1000e: make E1000E default to the same kconfig setting as E1000
Date: Sat, 15 Dec 2007 01:02:34 +0100 [thread overview]
Message-ID: <20071215000234.GB5403@stusta.de> (raw)
In-Reply-To: <47630F23.5060403@garzik.org>
On Fri, Dec 14, 2007 at 06:17:55PM -0500, Jeff Garzik wrote:
> Adrian Bunk wrote:
>> On Fri, Dec 14, 2007 at 03:39:26PM -0500, Jeff Garzik wrote:
>>> akpm@linux-foundation.org wrote:
>>>> From: Randy Dunlap <randy.dunlap@oracle.com>
>>> ...
>>> So I think the breakage that occurs is mitigated by two factors:
>>> 1) kernel hackers that do their own configs are expected to be able to
>>> figure this stuff.
>>> 2) kernel builders (read: distros, mainly) are expected to have put
>>> thought into the Kconfig selection and driver migration strategies.
>>> ...
>>> I would prefer simply to communicate to kernel experts and builders about
>>> a Kconfig issue that could potentially their booting/networking...
>>> because this patch is only needed if the kernel experts do not already
>>> know about a necessary config update.
>>
>> You miss the vast majority of kconfig users:
>>
>> 3) system administrators etc. who for different reasons compile their own
>> kernels but neither are nor want to be kernel developers
>>
>> There's a reason why e.g. LPI requires you to be able to compile your own
>> kernel even for getting a "Junior Level Linux Professional" certificate.
>
> Great!
>
>
>> Or that one of the authors of "Linux Device drivers" has written a book
>> covering only how to build and run your own kernel.
>
> Nonetheless, it will always be true that configuring your own kernel
> requires knowledge of the options you are setting.
We are not talking about Aunt Tillie, "system administrator" is the use
case that might cover this (quite diverse) group of users best.
We can expect kconfig users to know what filesystems their data is on
and to have some knowledge of their hardware, but every other knowledge
we must give through kconfig.
> Jeff
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2007-12-15 0:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-14 0:02 [patch 01/10] e1000e: make E1000E default to the same kconfig setting as E1000 akpm
2007-12-14 20:39 ` Jeff Garzik
2007-12-14 22:39 ` Adrian Bunk
2007-12-14 23:17 ` Jeff Garzik
2007-12-15 0:02 ` Adrian Bunk [this message]
2007-12-14 23:22 ` Andrew Morton
2007-12-14 23:54 ` Stephen Hemminger
2007-12-15 4:57 ` Bill Fink
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=20071215000234.GB5403@stusta.de \
--to=bunk@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=auke-jan.h.kok@intel.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
/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).