From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: "Karicheri, Muralidharan" <m-karicheri2@ti.com>
Cc: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"khilman@deeprootsystems.com" <khilman@deeprootsystems.com>
Subject: Re: [PATCH v3 1/6] V4L - vpfe capture - header files for ISIF driver
Date: Tue, 02 Feb 2010 16:01:47 -0200 [thread overview]
Message-ID: <4B68688B.80207@redhat.com> (raw)
In-Reply-To: <A69FA2915331DC488A831521EAE36FE401630F31AB@dlee06.ent.ti.com>
Karicheri, Muralidharan wrote:
> Mauro,
>
>>> How to request sign-off? Do I only send patches
>>> to the person, not to the list?
>
> I think you have not answered this.
>> For the patches exchanged via the ML, I need some scriptable way to mark
>> them
>> as RFC at the Patchwork.
>>
>> So, adding [RFC PATCH] or [PATCH RFC] works. It also works if you add
>> something
>> like [PATCH OMAP] or [PATCH OMAP V4L], and provided that all other
>> contributors
>> to the patches you'll be sending me a pull request do exactly the same.
>
>
> Not sure what the last part of your statement (beginning with "provided that") means.
I mean: the better is if everybody sending such patches to do the same way. So, it
would be really good if all traffic at the ML for those RFC patches to have the
same tag.
> The patches always go through multiple iterations. In future
> I will add [RFC PATCH] for such patches. But this request was sent to Kevin
> to ack my patches so that I can send a pull request. How do I handle this?
> A direct email to Kevin without copying to linux-media ?
You don't need to c/c the linux-media ML for it, but, of course you can do it.
Anyway, at the pull requests that are touching on arch, please C/C the arch
maintainer on it (even having their SOB). This will help them to track what's
happening on the files under their responsibility.
--
Cheers,
Mauro
next prev parent reply other threads:[~2010-02-02 18:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-01 22:27 [PATCH v3 6/6] DaVinci - Adding platform & board changes for vpfe capture on DM365 m-karicheri2
2010-02-01 22:27 ` [PATCH v3 5/6] V4L - vpfe capture - build environment for isif driver m-karicheri2
2010-02-01 22:27 ` [PATCH v3 1/6] V4L - vpfe capture - header files for ISIF driver m-karicheri2
2010-02-01 22:27 ` [PATCH v3 2/6] V4L - vpfe capture - source for ISIF driver on DM365 m-karicheri2
2010-02-01 22:27 ` [PATCH v3 3/6] V4L - vpfe capture - vpss driver enhancements for DM365 m-karicheri2
2010-02-01 22:27 ` [PATCH v3 4/6] V4L - vpfe_capture - bug fixes and enhancements m-karicheri2
2010-02-01 22:33 ` [PATCH v3 1/6] V4L - vpfe capture - header files for ISIF driver Karicheri, Muralidharan
2010-02-01 23:12 ` Mauro Carvalho Chehab
2010-02-02 15:50 ` Karicheri, Muralidharan
2010-02-02 17:10 ` Mauro Carvalho Chehab
2010-02-02 17:50 ` Karicheri, Muralidharan
2010-02-02 18:01 ` Mauro Carvalho Chehab [this message]
2010-02-03 17:34 ` [PATCH v3 6/6] DaVinci - Adding platform & board changes for vpfe capture on DM365 Karicheri, Muralidharan
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=4B68688B.80207@redhat.com \
--to=mchehab@redhat.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-media@vger.kernel.org \
--cc=m-karicheri2@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