public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Jiri Kosina <jkosina@suse.cz>,
	linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
	marauder@tiscali.it
Subject: Re: [PATCH V2]NEXT:drivers:staging:media Fix comments and some typos in staging/media/*
Date: Fri, 16 Mar 2012 09:06:44 -0700	[thread overview]
Message-ID: <4F636514.1080303@gmail.com> (raw)
In-Reply-To: <20120316155845.GA975@kroah.com>

On 03/16/2012 08:58 AM, Greg KH wrote:
> On Fri, Mar 16, 2012 at 04:45:03PM +0100, Jiri Kosina wrote:
>> On Fri, 16 Mar 2012, Justin P. Mattock wrote:
>>
>>> before I forget about this patch, what was the status of this one?
>>
>> As previously announced multiple times, I am ignoring patches that go to
>> drivers/staging and letting Greg pick them up if he wants to.
>>
>> Greg, if you want to have this changed, just let me know.
>
> No, no objection from me, but patches to drivers/staging/media/ do not
> go through me, please see the MAINTAINERS file for the owner of those
> (hint, it's Mauro...)
>
> thanks,
>
> greg k-h
>

ahh!! I got it now.. your in charge of the staging tree but for each 
branch there is an owner(I thought to just send to greg KH and thats it)

adding Mauro to the Cc's so he can view the patch, then on any other 
patch I send to staging I will send it to the maintainer then the rest 
as follows with a cc's.

Thanks for the help on this.

Justin P. Mattock

  reply	other threads:[~2012-03-16 16:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-06 14:55 [PATCH V2]NEXT:drivers:staging:media Fix comments and some typos in staging/media/* Justin P. Mattock
2012-03-16 15:35 ` Justin P. Mattock
2012-03-16 15:45   ` Jiri Kosina
2012-03-16 15:48     ` Justin P. Mattock
2012-03-16 15:58     ` Greg KH
2012-03-16 16:06       ` Justin P. Mattock [this message]
2012-03-16 16:08         ` Justin P. Mattock
2012-03-19 17:27           ` Mauro Carvalho Chehab

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=4F636514.1080303@gmail.com \
    --to=justinmattock@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jkosina@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=marauder@tiscali.it \
    /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