From: Finn Thain <fthain@telegraphics.com.au>
To: Marc Gonzalez <marc.w.gonzalez@free.fr>
Cc: Douglas Gilbert <dgilbert@interlog.com>,
Bart Van Assche <bvanassche@acm.org>,
James Bottomley <jejb@linux.ibm.com>,
Martin Petersen <martin.petersen@oracle.com>,
SCSI <linux-scsi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v1] scsi: Don't select SCSI_PROC_FS by default
Date: Sat, 22 Jun 2019 09:50:24 +1000 (AEST) [thread overview]
Message-ID: <alpine.LNX.2.21.1906220920320.180@nippy.intranet> (raw)
In-Reply-To: <5d9d0851-f864-6d78-7e7d-9d018bea5704@free.fr>
On Fri, 21 Jun 2019, Marc Gonzalez wrote:
> On 21/06/2019 01:43, Finn Thain wrote:
>
> > On Thu, 20 Jun 2019, Marc Gonzalez wrote:
> >
> >> How likely is it that distro kernels would *not* enable CHR_DEV_SG?
> >> (Distros tend to enable everything, and then some.)
> >
> > How likely is it that embedded developers would *not* disable
> > CHR_DEV_SG? They tend to disable everything, and then enable only what
> > they need.
>
> I don't see where you're going with this line of reasoning?
>
Exactly. This sort of reasoning goes nowhere.
> Below is my current (as of next-20190612) defconfig.
>
> Notice the options marked as "not set". These are options that are
> enabled by default (and which I've disabled).
>
> Everyone thinks "their" option is critical (and it is, *to them*) but,
> in fact, few really are -- universally.
The relevant policy is documented in
Documentation/kbuild/kconfig-language.txt.
If there are useful generalizations about the choice of defaults for
Kconfig symbols (or changing those defaults) that are not documented then
they probably should be.
--
next prev parent reply other threads:[~2019-06-21 23:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 13:59 [PATCH v1] scsi: Don't select SCSI_PROC_FS by default Marc Gonzalez
2019-06-17 21:11 ` Bart Van Assche
2019-06-18 0:35 ` Douglas Gilbert
2019-06-18 1:08 ` Finn Thain
2019-06-18 7:29 ` Marc Gonzalez
2019-06-18 15:31 ` Douglas Gilbert
2019-06-19 9:42 ` Marc Gonzalez
2019-06-19 14:34 ` Douglas Gilbert
2019-06-20 9:01 ` Marc Gonzalez
2019-06-20 21:47 ` Martin K. Petersen
2019-06-20 23:43 ` Finn Thain
2019-06-21 10:41 ` Marc Gonzalez
2019-06-21 23:50 ` Finn Thain [this message]
2019-06-18 3:28 ` Bart Van Assche
2019-06-18 17:43 ` Elliott, Robert (Servers)
2019-07-05 7:22 ` Hannes Reinecke
2019-07-05 17:53 ` Douglas Gilbert
[not found] ` <284c3ecc-b3a8-eeec-92d5-5eda1f20f691@suse.de>
2019-07-08 13:02 ` Douglas Gilbert
2019-07-05 7:18 ` Hannes Reinecke
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=alpine.LNX.2.21.1906220920320.180@nippy.intranet \
--to=fthain@telegraphics.com.au \
--cc=bvanassche@acm.org \
--cc=dgilbert@interlog.com \
--cc=hch@lst.de \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=marc.w.gonzalez@free.fr \
--cc=martin.petersen@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