public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@kernel.org>
To: David Brownell <david-b@pacbell.net>
Cc: Al Boldi <a1426z@gawab.com>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	Greg KH <greg@kroah.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] USB Kconfig: Reorganize USB Kconfig Menu
Date: Sat, 29 Dec 2007 01:34:50 +0200	[thread overview]
Message-ID: <20071228233450.GC9105@does.not.exist> (raw)
In-Reply-To: <200712271418.59156.david-b@pacbell.net>

On Thu, Dec 27, 2007 at 02:18:58PM -0800, David Brownell wrote:
> On Sunday 23 December 2007, Al Boldi wrote:
> > 
> > Reogranize USB Kconfig Menu, and move USB_GADGET out into the Device Driver
> > Menu.  This helps the USB Kconfig Menu to be more logical/usable.
> > 
> > Cc: David Brownell <david-b@pacbell.net>
> > Cc: Greg KH <greg@kroah.com>
> > Cc: Andrew Morton <akpm@linux-foundation.org>
> > Signed-off-by: Al Boldi <a1426z@gawab.com>
> 
> Along those lines, sure ... but this particular patch can't quite
> be the answer.  For one thing, it rather critially needs the appended,
> else it won't work on ARM.  (And quite a lot of the ARM platforms
> need the gadget stack!!)
> 
> There are ISTR a few other platforms which, for reasons unknown to
> me, don't source drivers/Kconfig but recreate portions of it on
> their own ... that's not something that this patch should change.

$ find . -name Kconfig\* | xargs grep drivers/usb/Kconfig
./arch/arm/Kconfig:source "drivers/usb/Kconfig"
./arch/cris/Kconfig:source "drivers/usb/Kconfig"
./arch/h8300/Kconfig:source "drivers/usb/Kconfig"
./arch/v850/Kconfig:source "drivers/usb/Kconfig"
./drivers/Kconfig:source "drivers/usb/Kconfig"
$ 

> Also, looking at this in xconfig shows some oddness.  That "core"
> submenu holds stuff that would logically be part of the toplevel
> menu for host side USB.  While that toplevel menu has the USS720
> driver, which seems more like a "miscellany" thing...
> 
> The comment about SCSI shouldn't show when SCSI is defined; and
> the comment aboue "SCSI disk support" belongs with the mass storage
> menu, not at the top level.  The way that the mass storage menu
> is presented also hides the fact that you can get fully functional
> mass storage support without checking *any* of the drivers there,
> since the core already handles standard devices.
>...

The SCSI dependency should be handled through select - there's no 
reason for bothering the kconfig user wih such implementation details.

> - Dave
>...


cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2007-12-28 23:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-23 11:49 [PATCH] USB Kconfig: Reorganize USB Kconfig Menu Al Boldi
2007-12-23 12:37 ` Jan Engelhardt
2007-12-23 13:15   ` Al Boldi
2007-12-23 15:25     ` Jan Engelhardt
2007-12-23 15:27       ` Jan Engelhardt
2007-12-27 22:18 ` David Brownell
2007-12-28 23:34   ` Adrian Bunk [this message]
2007-12-30 19:09     ` Al Boldi

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=20071228233450.GC9105@does.not.exist \
    --to=bunk@kernel.org \
    --cc=a1426z@gawab.com \
    --cc=akpm@linux-foundation.org \
    --cc=david-b@pacbell.net \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@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