From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Mathias Nyman <mathias.nyman@linux.intel.com>
Cc: Andrew Bresticker <abrestic@chromium.org>,
Mathias Nyman <mathias.nyman@intel.com>,
Alan Stern <stern@rowland.harvard.edu>,
Julius Werner <jwerner@chromium.org>,
Gregory CLEMENT <gregory.clement@free-electrons.com>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
Stephen Warren <swarren@wwwdotorg.org>,
Thierry Reding <thierry.reding@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: [PATCH v3 0/4] Allow xHCI drivers to be built as separate modules
Date: Thu, 2 Oct 2014 09:23:57 -0700 [thread overview]
Message-ID: <20141002162357.GA32555@kroah.com> (raw)
In-Reply-To: <542D7DC7.90300@linux.intel.com>
On Thu, Oct 02, 2014 at 07:31:03PM +0300, Mathias Nyman wrote:
> On 09/09/2014 05:27 PM, Mathias Nyman wrote:
> > On 09/03/2014 10:51 PM, Andrew Bresticker wrote:
> >> Mathias,
> >>
> >> On Tue, Aug 19, 2014 at 10:01 AM, Andrew Bresticker
> >> <abrestic@chromium.org> wrote:
> >>> It was suggested in the review of the Tegra xHCI driver [1] that we
> >>> allow xHCI drivers to be built as individual modules (like EHCI) instead
> >>> of building them all into the single xhci-hcd module as they are today.
> >>>
> >>> Patches 1-3 prepare for making the xHCI PCI and platform drivers able
> >>> to be built as individual modules and patch 4 actually creates the 3
> >>> separate modules (core, platform, PCI).
> >>>
> >>> Based on 3.17-rc1.
> >>>
> >>> Changes from v2:
> >>> - fixed typo in xhci_register_plat
> >>> - exported another symbol needed by xhci-pci module
> >>> Changes from v1:
> >>> - rebased on changes introduced by xhci-rcar driver
> >>>
> >>> [1] http://patchwork.ozlabs.org/patch/361265/
> >>>
> >>> Andrew Bresticker (4):
> >>> xhci: Introduce xhci_init_driver()
> >>> xhci: Check for XHCI_COMP_MODE_QUIRK when disabling D3cold
> >>> xhci: Export symbols used by host-controller drivers
> >>> xhci: Allow xHCI drivers to be built as separate modules
> >>
> >> Any thoughts/comments on this series?
> >>
> >>
> >
> > Sorry about the delay.
> > When I start looking at this I always get interrupted by some fire that needs to be put out.
> >
> > I still need some more time to go through it
> >
> > -Mathias
> >
> > --
> >
>
> Ok, finally found the time to look through it. Sorry about the long wait
>
> The whole series look good, and its now more in line with how ehci does things (like using *hci_init_driver())
>
> Series still apply nicely on usb-next.
>
> Greg, any chance this still can get to your usb-next and to the 3.18 merge window?
> Tegra developers seem eager to get it in, and I feel bad for not reviewing it earlier.
They aren't in my patch queue anymore, so please send them, with your
signed-off-by, and I will try to get them in.
greg k-h
prev parent reply other threads:[~2014-10-02 16:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-19 17:01 Andrew Bresticker
2014-08-19 17:01 ` [PATCH v3 1/4] xhci: Introduce xhci_init_driver() Andrew Bresticker
2014-08-19 17:01 ` [PATCH v3 2/4] xhci: Check for XHCI_COMP_MODE_QUIRK when disabling D3cold Andrew Bresticker
2014-08-19 17:01 ` [PATCH v3 3/4] xhci: Export symbols used by host-controller drivers Andrew Bresticker
2014-08-19 17:01 ` [PATCH v3 4/4] xhci: Allow xHCI drivers to be built as separate modules Andrew Bresticker
2014-09-03 19:51 ` [PATCH v3 0/4] " Andrew Bresticker
2014-09-09 14:27 ` Mathias Nyman
2014-10-02 16:31 ` Mathias Nyman
2014-10-02 16:23 ` Greg Kroah-Hartman [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=20141002162357.GA32555@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=abrestic@chromium.org \
--cc=gregory.clement@free-electrons.com \
--cc=jwerner@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=mathias.nyman@linux.intel.com \
--cc=stern@rowland.harvard.edu \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.com \
--cc=yoshihiro.shimoda.uh@renesas.com \
/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
Powered by JetHome