From: Igor Grinberg <grinberg@compulab.co.il>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: balbi@ti.com, Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Keshava Munegowda <Keshava_mgowda@ti.com>,
linux-usb@vger.kernel.org, linux-omap@vger.kernel.org,
Samuel Ortiz <sameo@linux.intel.com>
Subject: Re: [PATCH] ARM: OMAP: USB: fix warning on EHCI PHY reset path
Date: Mon, 07 May 2012 17:27:50 +0300 [thread overview]
Message-ID: <4FA7DBE6.3060809@compulab.co.il> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1205071003240.1602-100000@iolanthe.rowland.org>
On 05/07/12 17:04, Alan Stern wrote:
> On Sun, 6 May 2012, Igor Grinberg wrote:
>
>> Hi Alan,
>
> ...
>
>> Sorry, for being jumpy...
>> Samuel has not answered yet (it has been more then two weeks already)
>> and I'd like this to go into 3.5.
>> Also, the dependency patch is already in Linus' tree. It has been merged with
>> fixes (I thought it will happen only during the merge window...).
>>
>> Can you, please take this one?
>
> No, I can't, sorry. It has to be accepted by Greg KH.
Hmm... I don't mind it be that way, but I'd like to understand:
# scripts/get_maintainer.pl -f drivers/usb/host/ehci-omap.c
Alan Stern <stern@rowland.harvard.edu> (maintainer:USB EHCI DRIVER)
Felipe Balbi <balbi@ti.com> (maintainer:OMAP USB SUPPORT)
Greg Kroah-Hartman <gregkh@suse.de> (supporter:USB SUBSYSTEM)
linux-usb@vger.kernel.org (open list:USB EHCI DRIVER)
linux-omap@vger.kernel.org (open list:OMAP USB SUPPORT)
linux-kernel@vger.kernel.org (open list)
This makes you the USB EHCI maintainer, right?
I just want to understand...
Do you need also ack from Greg to take something to your tree
for being applied in the next merge window?
--
Regards,
Igor.
next prev parent reply other threads:[~2012-05-07 14:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-27 14:08 [PATCH] ARM: OMAP: USB: fix warning on EHCI PHY reset path Igor Grinberg
2012-03-28 8:52 ` Felipe Balbi
2012-03-28 10:53 ` Raja, Govindraj
[not found] ` <CAMrsUdJjwAN4haHOkrGfrpb9HnbsMLyUE4a5aLnCPKC2JdUt_A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-03-28 11:33 ` Igor Grinberg
2012-03-28 12:01 ` Munegowda, Keshava
[not found] ` <4F72E1F9.3020400@ti.com>
2012-03-28 11:13 ` Igor Grinberg
2012-03-28 13:04 ` Shubhrajyoti Datta
2012-04-19 14:10 ` Igor Grinberg
[not found] ` <4F901CCC.9000703-UTxiZqZC01RS1MOuV/RT9w@public.gmane.org>
2012-04-19 15:01 ` Alan Stern
2012-04-20 11:57 ` Felipe Balbi
2012-05-06 6:25 ` Igor Grinberg
2012-05-07 8:09 ` Samuel Ortiz
2012-05-07 11:46 ` Igor Grinberg
[not found] ` <4FA7B61B.3020604-UTxiZqZC01RS1MOuV/RT9w@public.gmane.org>
2012-05-07 12:17 ` Samuel Ortiz
[not found] ` <4FA61941.5080603-UTxiZqZC01RS1MOuV/RT9w@public.gmane.org>
2012-05-07 14:04 ` Alan Stern
2012-05-07 14:27 ` Igor Grinberg [this message]
[not found] ` <4FA7DBE6.3060809-UTxiZqZC01RS1MOuV/RT9w@public.gmane.org>
2012-05-07 14:48 ` Alan Stern
[not found] ` <Pine.LNX.4.44L0.1205071046350.1602-100000-IYeN2dnnYyZXsRXLowluHWD2FQJk+8+b@public.gmane.org>
2012-05-08 7:53 ` Igor Grinberg
[not found] ` <4FA8D108.7090004-UTxiZqZC01RS1MOuV/RT9w@public.gmane.org>
2012-05-08 16:24 ` Greg Kroah-Hartman
2012-05-09 6:25 ` Igor Grinberg
2012-05-09 7:31 ` Igor Grinberg
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=4FA7DBE6.3060809@compulab.co.il \
--to=grinberg@compulab.co.il \
--cc=Keshava_mgowda@ti.com \
--cc=balbi@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sameo@linux.intel.com \
--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