From: Greg KH <greg@kroah.com>
To: Al Boldi <a1426z@gawab.com>
Cc: Stefan Richter <stefanr@s5r6.in-berlin.de>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
David Brownell <david-b@pacbell.net>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 0/5] USB Kconfig: Reorganize USB Kconfig Menu
Date: Mon, 14 Jan 2008 10:12:39 -0800 [thread overview]
Message-ID: <20080114181239.GB14814@kroah.com> (raw)
In-Reply-To: <200801141321.51185.a1426z@gawab.com>
On Mon, Jan 14, 2008 at 01:21:51PM +0300, Al Boldi wrote:
> Stefan Richter wrote:
> > Greg KH wrote:
> > > On Sat, Jan 12, 2008 at 01:20:46PM +0300, Al Boldi wrote:
> > >> Greg KH wrote:
> > >>> On Sat, Jan 05, 2008 at 06:40:38PM +0300, Al Boldi wrote:
> > >>>> Reorganize USB Kconfig Menu, and move USB_GADGET out into the Device
> > >>>> Driver Menu. ?This helps the USB Kconfig Menu to be more
> > >>>> logical/usable.
> > >>>>
> > >>>> Patchset against 2.6.23
> > >>>
> > >>> So what was the final verdict in this patch set?
> > >>
> > >> IMHO, it's a lot better than what we have right now, and it's split up
> > >> so that you can pick and choose what you think is useful.
> > >>
> > >>> Can you rsend this against 2.6.24-rc7 with the requested changes (if
> > >>> any) in it?
> > >>
> > >> The only critical change is in patch 2/5:
> > >>
> > >> menuconfig USB_STORAGE
> > >> tristate "USB Mass Storage support"
> > >> - depends on USB && SCSI
> > >> + depends on USB && BLOCK
> > >> + select SCSI
> > >>
> > >>
> > >> I was hoping you could take care of it, or maybe wait until 2.6.25 is
> > >> out.
> > >
> > > Well, if you want such a change to go into 2.6.25, I need the patches
> > > now :)
> > >
> > > So, can you respin these against 2.6.24-rc7, with the above fix, so that
> > > I can apply them and test them out?
> >
> > May I repeat my request that nobody does "select SCSI", please?
> >
> > Al Boldy, would you please explain like I asked you:
> > - what is wrong with the current solution which tells the user to
> > first enable SCSI to get the USB_STORAGE option,
> > - whether there are frequent end-user requests which demonstrate
> > that many people currently don't realize how to enable USB_STORAGE.
> >
> > Please use "select" carefully, particularly *only* for options which
> > enable simple compact library-like code which
> > - is small,
> > - doesn't itself depend on anything,
> > - doesn't has further configuration options in some other menu.
> > None of this applies to CONFIG_SCSI.
>
> I thought we discussed this before. We do it here, for the same reasons
> libata does it. In any case, the patch is optional.
Yes, I do not want to do this, as we went round and round on it in the
past many times over the years. It should be left as-is.
thanks,
greg k-h
next prev parent reply other threads:[~2008-01-14 18:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-05 15:40 Al Boldi
2008-01-11 22:39 ` Greg KH
2008-01-12 10:20 ` Al Boldi
2008-01-12 19:53 ` Greg KH
2008-01-13 11:05 ` Al Boldi
2008-01-13 11:50 ` Stefan Richter
2008-01-13 18:03 ` Randy Dunlap
2008-01-14 10:21 ` Al Boldi
2008-01-14 18:12 ` Greg KH [this message]
2008-01-14 19:49 ` 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=20080114181239.GB14814@kroah.com \
--to=greg@kroah.com \
--cc=a1426z@gawab.com \
--cc=akpm@linux-foundation.org \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.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®