From: Greg KH <gregkh@suse.de>
To: Tomas Winkler <tomasw@gmail.com>
Cc: Mauro Carvalho Chehab <mchehab@redhat.com>,
devel@driverdev.osuosl.org,
Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [PATCH 0/3] Move media staging drivers to staging/media
Date: Thu, 17 Nov 2011 11:22:16 -0800 [thread overview]
Message-ID: <20111117192216.GA32280@suse.de> (raw)
In-Reply-To: <CA+i0qc6yCjo+abxf8L5LvLqUfXPE8xN0fBqaFigLAmgXLNZvqg@mail.gmail.com>
On Thu, Nov 17, 2011 at 09:10:27PM +0200, Tomas Winkler wrote:
> On Thu, Nov 17, 2011 at 8:09 PM, Greg KH <gregkh@suse.de> wrote:
> > On Thu, Nov 17, 2011 at 07:47:50PM +0200, Tomas Winkler wrote:
> >> On Wed, Nov 2, 2011 at 5:10 PM, Greg KH <gregkh@suse.de> wrote:
> >> > On Wed, Nov 02, 2011 at 09:45:09AM -0200, Mauro Carvalho Chehab wrote:
> >> >> Greg,
> >> >>
> >> >> As agreed, this is the patches that move media drivers to their
> >>
> >> I've probably missed the news so I'd like ask what is the current
> >> patch flow for staging/media?
> >> Are the patches applied first to linux-media and then merged to the
> >> greg's staging tree or the staging tree remains the first sync point?
> >
> > Mauro handles all of the drivers/staging/media/ patches, I'm going to
> > just ignore them all, or, worse case, just bounce them to him :)
>
> Thanks for clarification. One more thing should I also omit posting to
> the driverdev mailing list?
Probably, I doubt anyone there cares about these drivers, but hey, it
can't hurt :)
thanks,
greg k-h
prev parent reply other threads:[~2011-11-17 19:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-02 11:45 [PATCH 0/3] Move media staging drivers to staging/media Mauro Carvalho Chehab
2011-11-02 15:10 ` Greg KH
2011-11-17 17:47 ` Tomas Winkler
2011-11-17 18:09 ` Greg KH
2011-11-17 19:10 ` Tomas Winkler
2011-11-17 19:22 ` Greg KH [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=20111117192216.GA32280@suse.de \
--to=gregkh@suse.de \
--cc=devel@driverdev.osuosl.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=tomasw@gmail.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