public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linux-usb@vger.kernel.org,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH, RFC 2/2] USB: host: make USB_ARCH_HAS_?HCI obsolete
Date: Tue, 4 Jun 2013 19:40:00 +0200	[thread overview]
Message-ID: <201306041940.00979.arnd@arndb.de> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1306041257250.1093-100000@iolanthe.rowland.org>

On Tuesday 04 June 2013, Alan Stern wrote:
> On Tue, 4 Jun 2013, Arnd Bergmann wrote:
> > so that would create a circular dependency unless we change all of them
> > at once. I did that when creating this patch, but then decided to
> > revert it for now and do smaller steps.
> 
> Okay.  Changing those 24 should be the next step.

Yes, and we can remove the various 'select USB_ARCH_HAS_*' from arch
code at the same time. Since there is no hurry, I would suggest doing
that after 3.11-rc1 so we don't have to worry about dependencies.
 
> > We could do
> > 
> > config USB_ARCH_HAS_HCD
> > 	def_bool USB_SUPPORT
> > 
> > or
> > 
> > config USB_ARCH_HAS_HCD
> > 	def_bool y
> > 
> > which would both have the exact same behavior as 'def_bool HAS_IOMEM'.
> 
> I'm in favor of "def_bool y".

Ok. And I'll use 'bool' for the 'USB_ARCH_HAS_?HCI' symbols since we
don't care about the value any more.

	Arnd

  reply	other threads:[~2013-06-04 17:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1733192.k73fhLUdvU@wuerfel>
2013-06-04 14:48 ` [PATCH, RFC 2/2] USB: host: make USB_ARCH_HAS_?HCI obsolete Arnd Bergmann
2013-06-04 15:22   ` Alan Stern
2013-06-04 15:38     ` Arnd Bergmann
2013-06-04 16:58       ` Alan Stern
2013-06-04 17:40         ` Arnd Bergmann [this message]
2013-06-04 17:42     ` [PATCH v2] usb: " Arnd Bergmann
2013-06-04 18:11       ` Alan Stern

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=201306041940.00979.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    /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