From: Greg KH <gregkh@suse.de>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Sarah Sharp <sarah.a.sharp@linux.intel.com>,
Grant Likely <grant.likely@secretlab.ca>,
linux-usb@vger.kernel.org, Felipe Balbi <balbi@ti.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 01/20] drivers_base: platform: use always ->name for uevent
Date: Tue, 23 Aug 2011 08:32:43 -0700 [thread overview]
Message-ID: <20110823153243.GB25968@suse.de> (raw)
In-Reply-To: <20110823095036.GA23284@linutronix.de>
On Tue, Aug 23, 2011 at 11:50:36AM +0200, Sebastian Andrzej Siewior wrote:
> * Greg KH | 2011-08-22 14:51:51 [-0700]:
>
> >> Greg, do you want to take this patch through your driver core tree, or
> >> would you prefer to have it come through the xHCI tree?
> >
> >I'll take it in my driver-core tree separate, as the others don't depend
> >on this one, right?
>
> Should the xhci series hit Linus' tree before your driver-core than
> rmmod of the xhci-pci driver will lead to a crash.
That's ok, just don't do that :)
And you can tell me to merge stuff with Linus after one of my other
trees is applied, I can do that as well.
greg k-h
next prev parent reply other threads:[~2011-08-23 15:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1313419901-13492-1-git-send-email-bigeasy@linutronix.de>
2011-08-15 14:51 ` [PATCH 01/20] drivers_base: platform: use always ->name for uevent Sebastian Andrzej Siewior
2011-08-15 14:56 ` Grant Likely
2011-08-15 15:13 ` Sebastian Andrzej Siewior
2011-08-15 15:17 ` Grant Likely
2011-08-15 15:17 ` Grant Likely
2011-08-22 21:41 ` Sarah Sharp
2011-08-22 21:51 ` Greg KH
2011-08-23 9:50 ` Sebastian Andrzej Siewior
2011-08-23 15:32 ` Greg KH [this message]
2011-09-30 13:29 ` Felipe Balbi
2011-09-30 17:09 ` Greg KH
2011-09-30 17:40 ` Felipe Balbi
2011-09-30 17:49 ` Greg KH
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=20110823153243.GB25968@suse.de \
--to=gregkh@suse.de \
--cc=balbi@ti.com \
--cc=bigeasy@linutronix.de \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sarah.a.sharp@linux.intel.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