From: Felipe Balbi <balbi@ti.com>
To: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: Paul Zimmerman <Paul.Zimmerman@synopsys.com>,
"balbi@ti.com" <balbi@ti.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Take dwc2 driver through Felipe's tree?
Date: Fri, 19 Sep 2014 16:08:38 -0500 [thread overview]
Message-ID: <20140919210837.GH19560@saruman.home> (raw)
In-Reply-To: <20140919210150.GA25927@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 1134 bytes --]
On Fri, Sep 19, 2014 at 02:01:50PM -0700, gregkh@linuxfoundation.org wrote:
> On Fri, Sep 19, 2014 at 08:52:07PM +0000, Paul Zimmerman wrote:
> > Hi Greg,
> >
> > How would you feel about Felipe taking the dwc2 driver into his tree?
> > There has been quite a bit of increased activity with dwc2 lately, and
> > I know you already have more than enough stuff on your plate already.
> > So this would mean one less thing for you to worry about. Plus it
> > would mean an extra layer of review before getting to you.
> >
> > I've already talked to Felipe about it, and he's fine with it. If
> > you're OK with it, I think I just need to send a patch adding a T:
> > line to the MAINTAINERS entry, showing Felipe's tree?
> >
> > I guess we would want to do this just before you close your USB tree,
> > and you could announce it then?
>
> No objection from me. I'm working in my patch backlog right now, should
> get through them by the end of the day, so feel free to send me a
> MAINTAINERS patch I can use.
alright, it's all set now. Starting on v3.18-rc, I'll start taking dwc2
on my tree.
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2014-09-19 21:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-19 20:52 Paul Zimmerman
2014-09-19 21:01 ` gregkh
2014-09-19 21:08 ` Felipe Balbi [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=20140919210837.GH19560@saruman.home \
--to=balbi@ti.com \
--cc=Paul.Zimmerman@synopsys.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
/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
all inboxes | Powered by JetHome®