mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Fabio Comolli" <fabio.comolli@gmail.com>
To: "Stefan Richter" <stefanr@s5r6.in-berlin.de>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	sam@ravnborg.org, James.Bottomley@hansenpartnership.com,
	linux-scsi@vger.kernel.org, "Matthew Wilcox" <matthew@wil.cx>
Subject: Re: Possible bug in SCSI Kconfig
Date: Wed, 22 Oct 2008 21:29:37 +0200	[thread overview]
Message-ID: <b637ec0b0810221229n636ef47er78f119617ef93085@mail.gmail.com> (raw)
In-Reply-To: <48FF726D.9060504@s5r6.in-berlin.de>

Hi.

On Wed, Oct 22, 2008 at 8:35 PM, Stefan Richter
<stefanr@s5r6.in-berlin.de> wrote:
> (adding Cc: LSML and author)
>
> On 10/22/2008, Fabio Comolli wrote at LKML:
>> Hi.
>> In kernel 2.6.27.2 - drivers/scsi/Kconfig we have:
>>
>> config SCSI_WAIT_SCAN
>>         tristate
>>         default m
>>         depends on SCSI
>>         depends on MODULES
>>
>> The tristate field is empty. This has the effect that this option is
>> not visible in menuconfig and so it's always selected. The default is
>> "m" for all architectures and so this module is always compiled if
>> SCSI and MODULES are both enabled.
>>
>> I'm using a patch like this one:
>>
>>  config SCSI_WAIT_SCAN
>> -     tristate
>> +     tristate "Wait until all the async scans are complete"
>>       default m
>>       depends on SCSI
>>       depends on MODULES
>>
>> to get rid of that module.
>>
>> Of course, I have no idea if this is correct or the current behavior
>> is the expected one.
>>
>> Regards,
>> Fabio
>
> What's the correct behaviour is contentious.  There have been complaints
> that it shouldn't be built if it is not needed.  However, how it
> currently works is how those who added and merged that feature thought
> that it should be.
>
> Notes on your suggestion:
>
>  - If you make it a visible prompt, you should also add a help text.
>    No Kconfig prompts without good help text, please!
>
>  - The suggested prompt text doesn't describe the matter too well.
>    scsi_wait_scan rather is a module which userland can use to get
>    a signal for when scans (by some but not all transports) are done.
>    (The signal is the end of module initialization of the
>    scsi_wait_scan module.)  I.e. the kernel as a whole doesn't
>    necessarily wait, just this module does.
>

Well, I didn't mean to have the patch merged. My point was just to
understand if the Kconfig was correct.

> You could use the comment in drivers/scsi/scsi_wait_scan.c and the
> changelog of
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=3e082a910d217b2e7b186077ebf5a1126a68c62f
> as a basis for the Kconfig help text.  You could actually add a help
> text even to invisible prompts, just for documentation purposes.

Well, the first line of comment in that file reads "This is a simple
module to wait until all the async scans are complete." More or less
the text I added to the tristate.

> --
> Stefan Richter
> -=====-==--- =-=- =-==-
> http://arcgraph.de/sr/
>

Regards,
Fabio

  reply	other threads:[~2008-10-22 19:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-22 16:29 Fabio Comolli
2008-10-22 18:35 ` Stefan Richter
2008-10-22 19:29   ` Fabio Comolli [this message]
2008-10-22 19:05 ` James Bottomley
2008-10-22 19:25   ` Fabio Comolli
2008-10-22 19:26     ` Matthew Wilcox
2008-10-22 19:31       ` Fabio Comolli
2008-10-22 19:34         ` Matthew Wilcox
2008-10-22 19:45           ` Fabio Comolli
2008-10-22 19:44     ` James Bottomley
2008-10-22 19:48       ` Fabio Comolli
2008-10-23 17:30       ` Stefan Richter
2008-10-23 17:39         ` Matthew Wilcox
2008-10-23 18:59           ` Stefan Richter

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=b637ec0b0810221229n636ef47er78f119617ef93085@mail.gmail.com \
    --to=fabio.comolli@gmail.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=matthew@wil.cx \
    --cc=sam@ravnborg.org \
    --cc=stefanr@s5r6.in-berlin.de \
    /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

all inboxes | Powered by JetHome®