All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Gadiyar, Anand" <gadiyar@ti.com>
To: Greg KH <greg@kroah.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	"Balbi, Felipe" <balbi@ti.com>, Tony Lindgren <tony@atomide.com>,
	Greg Kroah-Hartman <gregkh@suse.de>
Subject: RE: [PATCH] MAINTAINERS: add myself as co-maintainer for OMAP USB
Date: Thu, 18 Aug 2011 21:00:55 +0530	[thread overview]
Message-ID: <ADF30F4D7BDE934D9B632CE7D5C7ACA4047C4D3ADEE8@dbde03.ent.ti.com> (raw)
In-Reply-To: <20110818145507.GA7012@kroah.com>

Greg KH wrote:
> On Thu, Aug 18, 2011 at 04:18:24PM +0530, Anand Gadiyar wrote:
> > I'd like to help co-maintain OMAP USB support. I've helped
> > out in the past when Felipe was away and would like make
> > it official.
> 
> Traditionally people are asked to be a maintainer, or they volunteer to
> take over unmaintained projects.  The only time I've see co-maintainers,
> is for larger projects, and then, it was a group decision.
> 

I was asked, by Felipe among others, to help maintain OMAP USB
support. The reason was to take some load off Felipe - I did not
take this up at that time due to other product pressures. I do
have more time on my hands now and would like to get back to
being more active in the community - I felt helping maintain
a driver was a good start.

Within TI, I've worked on debugging the EHCI, OHCI and
MUSB hardware for close to three years now and know more about
the controllers on OMAP than anyone else. I've acquired boards which
stress the several possible combinations of configurations possible
and usually help out with testing those corner cases.

> For something as "small" as musb, what is the benefit to anyone to have
> more than one maintainer?
>
> It seems to me that things are finally settling down with the recent
> musb mess, and I've been extremely happy with how Felipe has been
> handling things, and I honestly don't want to see that change at the
> moment.

It's less of MUSB, and more of the EHCI/OHCI - I don't believe
Felipe's familiar enough with the hardware to look after that.
Most contributions to the wrappers for those controllers have come
from Ajay Gupta, Keshava and me.


> So I'd stick with what we have now, unless you feel there are issues
> with how Felipe is handling things, and if so, you should take that up
> directly with him and only if that doesn't work out, me.

Nope - I'm happy with the way things are currently. So if Felipe no
longer feels the need to offload some of his maintainership work,
that's okay with me.

- Anand

      reply	other threads:[~2011-08-18 15:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-18 10:48 [PATCH] MAINTAINERS: add myself as co-maintainer for OMAP USB Anand Gadiyar
2011-08-18 10:48 ` Anand Gadiyar
2011-08-18 10:55 ` Felipe Balbi
2011-08-18 11:01   ` Gadiyar, Anand
2011-08-18 11:04     ` Felipe Balbi
2011-08-18 11:04       ` Felipe Balbi
2011-08-18 14:55 ` Greg KH
2011-08-18 14:55   ` Greg KH
2011-08-18 15:30   ` Gadiyar, Anand [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=ADF30F4D7BDE934D9B632CE7D5C7ACA4047C4D3ADEE8@dbde03.ent.ti.com \
    --to=gadiyar@ti.com \
    --cc=balbi@ti.com \
    --cc=greg@kroah.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.