All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Paul Mundt <lethal@linux-sh.org>
Cc: linux-next@vger.kernel.org,
	Sarah Sharp <sarah.a.sharp@linux.intel.com>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [PATCH -next] usb: xhci depends on PCI.
Date: Thu, 30 Apr 2009 09:13:14 -0700	[thread overview]
Message-ID: <20090430161314.GB18495@kroah.com> (raw)
In-Reply-To: <20090430083002.GA11456@linux-sh.org>

On Thu, Apr 30, 2009 at 05:30:02PM +0900, Paul Mundt wrote:
> While it looks like xhci was written with both PCI and non-PCI in mind,
> apparently only the former has seen any testing. xhci-mem.o can be "fixed"
> with a linux/dmapool.h include, but there are still parts of the code that
> make use of struct pci_dev directly. So, at least more work is needed before
> this can be turned on for non-PCI builds:

Thanks, you are correct.  I'll apply your Kconfig fix, thanks for making
it up.

greg k-h

      reply	other threads:[~2009-04-30 16:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-30  8:30 [PATCH -next] usb: xhci depends on PCI Paul Mundt
2009-04-30 16:13 ` Greg KH [this message]

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=20090430161314.GB18495@kroah.com \
    --to=greg@kroah.com \
    --cc=gregkh@suse.de \
    --cc=lethal@linux-sh.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sarah.a.sharp@linux.intel.com \
    --cc=sfr@canb.auug.org.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.