linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
	Adrian Bunk <bunk@kernel.org>, Ingo Molnar <mingo@elte.hu>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Greg KH <greg@kroah.com>
Subject: Re: [GIT PATCH] SCSI updates for 2.6.25
Date: Sat, 19 Apr 2008 14:45:11 -0600	[thread overview]
Message-ID: <20080419204511.GP20637@parisc-linux.org> (raw)
In-Reply-To: <alpine.LFD.1.10.0804191305360.2779@woody.linux-foundation.org>

On Sat, Apr 19, 2008 at 01:14:23PM -0700, Linus Torvalds wrote:
> So people: stop this total *idiocy* with "select is bad". It's not. The 
> lack of select is *much* worse.

Could we consider applying this patch then?

----

'select' not Considered Evil

While select should be used with care, it is not actually evil.

Signed-off-by: Matthew Wilcox <willy@linux.intel.com>

diff --git a/Documentation/kbuild/kconfig-language.txt b/Documentation/kbuild/kconfig-language.txt
index 649cb87..dacfcf2 100644
--- a/Documentation/kbuild/kconfig-language.txt
+++ b/Documentation/kbuild/kconfig-language.txt
@@ -104,9 +104,9 @@ applicable everywhere (see syntax).
   Reverse dependencies can only be used with boolean or tristate
   symbols.
   Note:
-	select is evil.... select will by brute force set a symbol
-	equal to 'y' without visiting the dependencies. So abusing
-	select you are able to select a symbol FOO even if FOO depends
+	select should be used with care.  It can set a symbol
+	without visiting the dependencies.  By abusing select you are
+	able to select a symbol FOO even if FOO depends
 	on BAR that is not set. In general use select only for
 	non-visible symbols (no prompts anywhere) and for symbols with
 	no dependencies. That will limit the usefulness but on the

-- 
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."

  reply	other threads:[~2008-04-19 20:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-18 17:41 [GIT PATCH] SCSI updates for 2.6.25 James Bottomley
2008-04-19 15:19 ` Ingo Molnar
2008-04-19 15:54   ` James Bottomley
2008-04-19 16:42     ` Ingo Molnar
2008-04-19 17:05     ` Adrian Bunk
2008-04-19 17:34       ` James Bottomley
2008-04-19 20:14         ` Linus Torvalds
2008-04-19 20:45           ` Matthew Wilcox [this message]
2008-04-20 14:09             ` Stefan Richter
2008-04-20 19:56               ` Matthew Wilcox
2008-04-20 20:14                 ` Stefan Richter
2008-04-28 21:00             ` Sam Ravnborg
2008-04-28 21:01               ` Matthew Wilcox
2008-04-19 22:27           ` James Bottomley
2008-04-19 23:14             ` Matthew Wilcox
2008-04-21 12:51             ` Ingo Molnar

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=20080419204511.GP20637@parisc-linux.org \
    --to=matthew@wil.cx \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=akpm@linux-foundation.org \
    --cc=bunk@kernel.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=torvalds@linux-foundation.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).