From: Greg KH <greg@kroah.com>
To: "Savoy, Pavan" <pavan_savoy@ti.com>
Cc: "gregkh@suse.de" <gregkh@suse.de>,
"alan@lxorguk.ukuu.org.uk" <alan@lxorguk.ukuu.org.uk>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3] prepare TI_ST to move out of staging
Date: Tue, 5 Oct 2010 13:07:20 -0700 [thread overview]
Message-ID: <20101005200720.GB4228@kroah.com> (raw)
In-Reply-To: <19F8576C6E063C45BE387C64729E739404AA21CB25@dbde02.ent.ti.com>
On Wed, Oct 06, 2010 at 12:40:33AM +0530, Savoy, Pavan wrote:
> Along with Bluetooth, we have some FM V4L2 patches which are being
> reviewed and re-submitted to the linux-media list, we will bring in
> them, once the linux-media ACKs them.
>
> They are intended for staging too, since there are few conflicts with
> other patches posted, I suppose it should be alright for them to go
> into the linux-next via your staging-next since the linux-media trees
> lags behind linux-next.
If you get an ack from the media maintainers, I can gladly take them.
thanks,
greg k-h
prev parent reply other threads:[~2010-10-05 20:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-30 20:13 [PATCH 0/3] prepare TI_ST to move out of staging pavan_savoy
2010-09-30 20:13 ` [PATCH 1/3] include:linux: tty.h: new ldisc for TI WiLink ST pavan_savoy
2010-09-30 20:13 ` [PATCH 2/3] drivers:staging:ti-st: drop the __KERNEL__ pavan_savoy
2010-09-30 20:13 ` [PATCH 3/3] drivers:staging:ti-st: mv ti_wilink_st header pavan_savoy
2010-10-05 18:23 ` [PATCH 0/3] prepare TI_ST to move out of staging Savoy, Pavan
2010-10-05 18:49 ` Greg KH
2010-10-05 18:57 ` Savoy, Pavan
2010-10-05 20:06 ` Greg KH
2010-10-05 19:10 ` Savoy, Pavan
2010-10-05 20:07 ` 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=20101005200720.GB4228@kroah.com \
--to=greg@kroah.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pavan_savoy@ti.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.