From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: halli manjunatha <manjunatha_halli@ti.com>
Cc: gregkh@suse.de, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org, Hans Verkuil <hverkuil@xs4all.nl>
Subject: Re: [RFC V10 3/7] drivers:media:radio: wl128x: FM Driver Common sources
Date: Wed, 19 Jan 2011 17:12:17 -0200 [thread overview]
Message-ID: <4D373791.5050000@infradead.org> (raw)
In-Reply-To: <AANLkTikRDWF5fyqixbJs+DRJN=aJGmgqmQOdVL_d9tPo@mail.gmail.com>
Manju,
Em 18-01-2011 11:19, halli manjunatha escreveu:
> have a look at the driver it’s already reviewed by Hans Verkuil.
> Please let me know if you are okay to include this in mainline.
As I've already pointed you, just send me a pull request from your tree when
you think it is ready. I'll be reviewing it after that. There are just too much
reviews on those drivers from TI for me to dig into every single version, especially
since, on most cases, I can't really contribute much, as I don't have OMAP3/Davinci
datasheets and the required devices here for testing, and that the reviews
come from someone at TI and/or one of your customers with a real test case
scenario.
So, as agreed in the past, I just mark all those drivers with RFC at patchwork
and I wait for the driver maintainer to send me a pull request, indicating me
that you've reached on a point where the driver/patch series is ready for its
addition.
So, if you think you're ready, you just need to send a pull request to the ML.
You don't even need to c/c me on that (and please avoid doing it, otherwise
I end by having multiple copies of your pull request, flooding my email with no
good reason).
Thanks,
Mauro
next prev parent reply other threads:[~2011-01-19 19:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-11 11:31 [RFC V10 0/7] FM V4L2 drivers for WL128x manjunatha_halli
2011-01-11 11:31 ` [RFC V10 1/7] drivers:media:radio: wl128x: FM Driver common header file manjunatha_halli
2011-01-11 11:17 ` Felipe Balbi
2011-01-11 11:31 ` [RFC V10 2/7] drivers:media:radio: wl128x: FM Driver V4L2 sources manjunatha_halli
2011-01-11 11:21 ` Felipe Balbi
2011-01-11 11:31 ` [RFC V10 3/7] drivers:media:radio: wl128x: FM Driver Common sources manjunatha_halli
2011-01-11 11:24 ` Felipe Balbi
2011-01-11 12:16 ` halli manjunatha
2011-01-11 12:42 ` Raja Mani
2011-01-17 10:15 ` halli manjunatha
2011-01-17 10:33 ` Hans Verkuil
2011-01-18 13:19 ` halli manjunatha
2011-01-19 19:12 ` Mauro Carvalho Chehab [this message]
2011-01-20 9:39 ` halli manjunatha
2011-01-11 11:31 ` [RFC V10 4/7] drivers:media:radio: wl128x: FM driver RX sources manjunatha_halli
2011-01-11 11:31 ` [RFC V10 5/7] drivers:media:radio: wl128x: FM driver TX sources manjunatha_halli
2011-01-11 11:31 ` [RFC V10 6/7] drivers:media:radio: wl128x: Kconfig & Makefile for wl128x driver manjunatha_halli
2011-01-11 11:30 ` Felipe Balbi
2011-01-11 11:31 ` [RFC V10 7/7] drivers:media:radio: Update Kconfig and Makefile for wl128x FM driver manjunatha_halli
2011-03-18 16:18 ` [PATCH -next] drivers:media:radio: wl128x: fix printk format and text Randy Dunlap
2011-03-22 18:23 ` 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=4D373791.5050000@infradead.org \
--to=mchehab@infradead.org \
--cc=gregkh@suse.de \
--cc=hverkuil@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=manjunatha_halli@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox