public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Ezequiel Garcia <elezegarcia@gmail.com>
Cc: Shubhrajyoti D <shubhrajyoti@ti.com>,
	linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
	julia.lawall@lip6.fr
Subject: Re: [PATCHv3 0/6] media: convert to c99 format
Date: Tue, 25 Sep 2012 08:09:26 -0300	[thread overview]
Message-ID: <1348571366.10028.4.camel@localhost.localdomain> (raw)
In-Reply-To: <CALF0-+UZGCpBcGFSyGirdAoKY5MGV-k6c9YefBHfvv5Qk=rTUg@mail.gmail.com>

Em Ter, 2012-09-25 às 08:03 -0300, Ezequiel Garcia escreveu:
> Shubhrajyoti,
> 
> Thanks for your patches.
> 
> I'm adding media maintainer (Mauro) in Cc. When you send
> patches for a file you should check who maintains them
> and put those people in Cc.

I actually prefer to not be c/c on the patches ;) Copying the
linux-media mailing list and checking if the patch was caught by
patchwork.linuxtv.kernel.org is enough, as I rely on patchwork to
queue patches for me. So, I just discard any media patch sent to me
directly.

> 
> This is really easy with get_maintainer.pl. You can also
> check with git log / git blame to see who has been working
> on that file.
> 
> You should read Documentation/SubmittingPatches
> if you haven't already (and read it again if you already have ;-)
> 
> On Tue, Sep 18, 2012 at 8:44 AM, Shubhrajyoti D <shubhrajyoti@ti.com> wrote:
> > The series tries to convert the i2c_msg to c99 struct.
> > This may avoid issues like below if someone tries to add an
> > element to the structure.
> > http://www.mail-archive.com/linux-i2c@vger.kernel.org/msg08972.html
> >
> > Special thanks to Julia Lawall for helping it automate.
> > By the below script.
> > http://www.mail-archive.com/cocci@diku.dk/msg02753.html
> >
> > Changelogs
> > - Remove the zero inititialisation of the flags.
> >
> > Shubhrajyoti D (6):
> >   media: Convert struct i2c_msg initialization to C99 format
> >   media: Convert struct i2c_msg initialization to C99 format
> >   media: Convert struct i2c_msg initialization to C99 format
> >   media: Convert struct i2c_msg initialization to C99 format
> >   media: Convert struct i2c_msg initialization to C99 format
> >   media: Convert struct i2c_msg initialization to C99 format
> >
> 
> IMO, sending several different patches with the same commit
> subject is not the best thing to do.
> 
> Perhaps this is too much to ask, but I'd prefer something
> like:
> 
> media: saa7706h: Convert struct i2c_msg initialization to C99 format
> 
> >  drivers/media/i2c/ks0127.c                    |   13 +++++++-
> >  drivers/media/i2c/msp3400-driver.c            |   40 +++++++++++++++++++++----
> >  drivers/media/i2c/tvaudio.c                   |   13 +++++++-
> >  drivers/media/radio/radio-tea5764.c           |   13 ++++++--
> >  drivers/media/radio/saa7706h.c                |   15 ++++++++-
> >  drivers/media/radio/si470x/radio-si470x-i2c.c |   23 ++++++++++----
> >  6 files changed, 96 insertions(+), 21 deletions(-)
> >
> 
> Thanks!
> Ezequiel.


  reply	other threads:[~2012-09-25 11:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-18 11:44 [PATCHv3 0/6] media: convert to c99 format Shubhrajyoti D
2012-09-18 11:44 ` [PATCHv3 1/6] media: Convert struct i2c_msg initialization to C99 format Shubhrajyoti D
2012-09-18 11:44 ` [PATCHv3 2/6] " Shubhrajyoti D
2012-09-18 11:44 ` [PATCHv3 3/6] " Shubhrajyoti D
2012-09-18 11:44 ` [PATCHv3 4/6] " Shubhrajyoti D
2012-09-18 11:44 ` [PATCHv3 5/6] " Shubhrajyoti D
2012-09-18 11:42   ` Felipe Balbi
2012-09-18 12:19     ` Shubhrajyoti
2012-09-18 11:44 ` [PATCHv3 6/6] " Shubhrajyoti D
2012-09-25 11:03 ` [PATCHv3 0/6] media: convert to c99 format Ezequiel Garcia
2012-09-25 11:09   ` Mauro Carvalho Chehab [this message]
2012-09-25 11:13     ` Ezequiel Garcia

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=1348571366.10028.4.camel@localhost.localdomain \
    --to=mchehab@redhat.com \
    --cc=elezegarcia@gmail.com \
    --cc=julia.lawall@lip6.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=shubhrajyoti@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