public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@ti.com>
To: Paul Zimmerman <Paul.Zimmerman@synopsys.com>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	"balbi@ti.com" <balbi@ti.com>, John Youn <John.Youn@synopsys.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"r.baldyga@samsung.com" <r.baldyga@samsung.com>,
	Marek Szyprowski <m.szyprowski@samsung.com>,
	Jingoo Han <jg1.han@samsung.com>,
	"dinguyen@opensource.altera.com" <dinguyen@opensource.altera.com>,
	Mian Yousaf Kaukab <yousaf.kaukab@intel.com>,
	Yunzhi Li <lyz@rock-chips.com>,
	Kever Yang <kever.yang@rock-chips.com>,
	Nick Hudson <skrll@netbsd.org>
Subject: Re: New maintainer for dwc2
Date: Mon, 12 Jan 2015 21:06:13 -0600	[thread overview]
Message-ID: <20150113030613.GA13988@saruman> (raw)
In-Reply-To: <A2CA0424C0A6F04399FB9E1CD98E030484506F64@US01WEMBX2.internal.synopsys.com>

[-- Attachment #1: Type: text/plain, Size: 1502 bytes --]

On Tue, Jan 13, 2015 at 01:17:48AM +0000, Paul Zimmerman wrote:
> > From: gregkh@linuxfoundation.org [mailto:gregkh@linuxfoundation.org]
> > Sent: Monday, January 12, 2015 5:02 PM
> > 
> > On Mon, Jan 12, 2015 at 11:14:54PM +0000, Paul Zimmerman wrote:
> > > Hi everyone,
> > >
> > > I will be leaving Synopsys on Friday, Jan 16th, so the dwc2 driver
> > > will need a new maintainer.
> > >
> > > I am recommending John Youn <johnyoun@synopsys.com> as the new
> > > maintainer.
> > >
> > > On the plus side, John has quite a bit of experience with the dwc2
> > > controller, and has previous experience submitting kernel patches (for
> > > the xhci and dwc3 drivers). And being a Synopsys employee, he will have
> > > access to internal resources for support.
> > >
> > > On the minus side, John has not worked directly with the in-kernel dwc2
> > > driver until very recently, and has not done maintainer work before.
> > >
> > > If no one has any objections, I will submit a patch to MAINTAINERS in a
> > > couple of days making John the new dwc2 maintainer.
> > 
> > I don't have any objections.  John will still be sending patches to
> > Felipe through email, and not directly to me, right?
> 
> Yes, that is correct.

right, that will not change and we already had a preliminary email
discussion privately a few weeks back. I have no objection on Paul's
recommendation either.

Thanks for all the help, Paul, over the last 2 years or so.

regards

-- 
balbi

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      reply	other threads:[~2015-01-13  3:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-12 23:14 New maintainer for dwc2 Paul Zimmerman
2015-01-13  1:02 ` gregkh
2015-01-13  1:17   ` Paul Zimmerman
2015-01-13  3:06     ` 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=20150113030613.GA13988@saruman \
    --to=balbi@ti.com \
    --cc=John.Youn@synopsys.com \
    --cc=Paul.Zimmerman@synopsys.com \
    --cc=dinguyen@opensource.altera.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jg1.han@samsung.com \
    --cc=kever.yang@rock-chips.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=lyz@rock-chips.com \
    --cc=m.szyprowski@samsung.com \
    --cc=r.baldyga@samsung.com \
    --cc=skrll@netbsd.org \
    --cc=yousaf.kaukab@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