mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Al Boldi <a1426z@gawab.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: sata & scsi suggestion for make menuconfig
Date: Sun, 9 Sep 2007 07:11:44 +0300	[thread overview]
Message-ID: <200709090711.44048.a1426z@gawab.com> (raw)
In-Reply-To: <200709081703.31280.a1426z@gawab.com>

Al Boldi wrote:
> Alan Cox wrote:
> > > I once sent a patch to make libata a submenu of scsi.
> >
> > Which is wrong
> >
> > Nakked-by: Alan Cox <alan@redhat.com>
> >
> > The general comments about moving this stuff around and making it
> > clearer what sd/sr etc are nowdays are good but hiding libata under SCSI
> > will cause even more confusion than it cures
>
> That's easy to fix:  just change the SCSI heading to include a libata
> hint.
>
> Something like this:
>
> [PATCH] libata Kconfig: Allow libata to be selected from within the SCSI
> submenu
>
> Move libata Kconfig sourcing from the drivers Kconfig into the SCSI
> Kconfig, and change the SCSI menu heading to indicate libata submenu
> inclusion.
>
> This allows the user to quickly select additional disk/tape/cdrom support
> from within the same menu.
>
> Signed-off-by: Al Boldi <a1426z@gawab.com>
> Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
> ---
> --- a/drivers/Kconfig   2007-05-02 17:25:30.000000000 +0300
> +++ b/drivers/Kconfig   2007-08-01 06:33:13.000000000 +0300
> @@ -22,8 +22,6 @@ source "drivers/ide/Kconfig"
>
>  source "drivers/scsi/Kconfig"
>
> -source "drivers/ata/Kconfig"
> -
>  source "drivers/cdrom/Kconfig"
>
>  source "drivers/md/Kconfig"
> --- a/drivers/scsi/Kconfig      2007-07-09 06:38:37.000000000 +0300
> +++ b/drivers/scsi/Kconfig      2007-08-01 06:46:42.000000000 +0300
> @@ -7,6 +7,8 @@ config RAID_ATTRS
>         ---help---
>           Provides RAID
>
> +source "drivers/ata/Kconfig"
> +
>  config SCSI
> -       tristate "SCSI device support"
> +       tristate "SCSI and Libata device support"
>         depends on BLOCK

Actually, this should have read:

--- a/drivers/scsi/Kconfig	2007-07-09 06:38:37.000000000 +0300
+++ a/drivers/scsi/Kconfig	2007-09-09 06:48:11.000000000 +0300
@@ -1,4 +1,4 @@
-menu "SCSI device support"
+menu "SCSI and Libata (SATA/PATA/new IDE) device support"
 
 config RAID_ATTRS
        tristate "RAID Transport Class"
@@ -7,6 +7,8 @@ config RAID_ATTRS
        ---help---
          Provides RAID
 
+source "drivers/ata/Kconfig"
+
 config SCSI
        tristate "SCSI device support"
        depends on BLOCK


I would think that with this minimal change it would make it crystal clear, 
to anybody who can read, where to enable libata support, and at the same 
time not to forget/overlook sd/sr selection.


Thanks!

--
Al


  parent reply	other threads:[~2007-09-09  4:11 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-08  3:52 Al Boldi
2007-09-08 13:47 ` Alan Cox
2007-09-08 14:03   ` Al Boldi
2007-09-08 16:08     ` Jan Engelhardt
2007-09-09  4:11     ` Al Boldi [this message]
     [not found] <90ZEn-1YU-3@gated-at.bofh.it>
     [not found] ` <918Rh-7Or-5@gated-at.bofh.it>
     [not found]   ` <919aD-8ua-7@gated-at.bofh.it>
2007-09-08 16:52     ` Bodo Eggert
2007-09-08 18:22       ` Stefan Richter
2007-09-08 18:54       ` Randy Dunlap
  -- strict thread matches above, loose matches on Subject: below --
2007-09-07 12:48 Folkert van Heusden
2007-09-07 14:40 ` Jan Engelhardt
2007-09-07 14:58   ` Folkert van Heusden
2007-09-07 19:38     ` Krzysztof Halasa
2007-09-07 23:02       ` Jan Engelhardt
2007-09-08  7:27         ` Jan Engelhardt
2007-09-07 15:35 ` Randy Dunlap
2007-09-07 15:59   ` Folkert van Heusden
2007-09-07 16:21     ` Stefan Richter
2007-09-07 23:05       ` Folkert van Heusden
2007-09-08  7:05         ` Stefan Richter
2007-09-08  7:29           ` Jan Engelhardt
2007-09-08  7:56             ` Stefan Richter
2007-09-08 16:31           ` Randy Dunlap
2007-09-08 16:44             ` Stefan Richter
2007-09-08 16:48               ` Randy Dunlap
2007-09-08 19:45                 ` Stefan Richter
2007-09-08  8:43   ` Sam Ravnborg
2007-09-13  8:50   ` Helge Hafting
2007-09-14 16:42     ` Goswin von Brederlow
2007-09-14 18:44       ` Stefan Richter
2007-09-08 16:07 ` Andi Kleen
2007-09-08 16:50   ` Randy Dunlap
2007-09-08 16:53     ` Matthew Wilcox
2007-09-08 18:13     ` Andi Kleen
2007-09-08 18:30       ` Stefan Richter
2007-09-08 19:14         ` Andi Kleen
2007-09-08 19:32           ` Stefan Richter
2007-09-09 21:00   ` James Bottomley
2007-09-09 21:03     ` Andi Kleen
2007-09-09 21:11       ` Jeff Garzik
2007-09-09 21:22         ` Andi Kleen
2007-09-09 21:39           ` James Bottomley
2007-09-10  6:38             ` Stefan Richter
2007-09-10 12:43               ` Rene Herman
2007-09-11 20:16           ` Bauke Jan Douma
2007-09-12 22:46         ` Adrian Bunk
2007-09-14 14:54           ` Stefan Richter
2007-09-14 15:15             ` Adrian Bunk
2007-09-14 15:37               ` Stefan Richter
2007-09-14 16:16                 ` Adrian Bunk
2007-09-14 16:50                   ` Stefan Richter
2007-09-15  8:04               ` Paul Rolland
2007-09-15  8:25                 ` Stefan Richter
2007-09-15 13:00                   ` Paul Rolland
2007-09-15 18:23                 ` david

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=200709090711.44048.a1426z@gawab.com \
    --to=a1426z@gawab.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®