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 15:10:15 -0200 [thread overview]
Message-ID: <4B685C77.8080805@redhat.com> (raw)
In-Reply-To: <A69FA2915331DC488A831521EAE36FE401630F3053@dlee06.ent.ti.com>
Karicheri, Muralidharan wrote:
> Mauro,
>
> If you scan the patch, you would see the status of this patch series.
Ok, but it is not script-able. So, I need to have an easy way to know when
a patch is still under discussion at the ML or if it is ready for merging.
I need something that I can write an script on my machine to update Patchwork
status and remove the stuff that are still under discussions from my pull queue.
On most cases, the level of detail between two revisions of the omap drivers
are due to some intrinsic details of the driver or the arch. So, it makes
no sense for me to keep checking all reviews. I would love to, but unfortunately
I have no spare time for it. That's why I prefer to review only the final revision,
when the patch is submitted.
>>> ---
>>> Applies to linux-next tree of v4l-dvb
>>> - rebasing to latest for merge (v3)
>
> Not sure if there is a better way to include this information. The arch part
> of this series requires sign-off from Kevin who is copied on this. I have
> seen your procedure for submitting patches and would send you an official
> pull request as per your procedure once Kevin sign-off the arch part.
The pull request is enough for me. I'll review when I receive it.
> I have following questions though..
>
> Should we always add [RFC PATCH] in the subject? It makes sense for
> patches being reviewed. How to request sign-off? Do I only send patches
> to the person, not to the list?
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.
I'll then write an specific script to mark those patches as RFC and remove from my
queue, until I receive your [PULL] request.
Cheers,
Mauro
next prev parent reply other threads:[~2010-02-02 17:10 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 [this message]
2010-02-02 17:50 ` Karicheri, Muralidharan
2010-02-02 18:01 ` Mauro Carvalho Chehab
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=4B685C77.8080805@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