From: Bhumika Goyal <bhumirks@gmail.com>
To: Mauro Carvalho Chehab <mchehab@s-opensource.com>
Cc: Julia Lawall <julia.lawall@lip6.fr>,
mchehab@kernel.org, hverkuil@xs4all.nl,
Jonathan Corbet <corbet@lwn.net>,
Kyungmin Park <kyungmin.park@samsung.com>,
kamil@wypas.org, a.hajda@samsung.com, bparrot@ti.com,
linux-media@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 00/10] [media] platform: make video_device const
Date: Sat, 26 Aug 2017 17:42:34 +0530 [thread overview]
Message-ID: <CAOH+1jH0BUgoyJK7=QUQcBMpqYf+W0TeMyJ+T2JSyxzY2Ha8fQ@mail.gmail.com> (raw)
In-Reply-To: <20170826085942.78e0d222@vento.lan>
On Sat, Aug 26, 2017 at 5:29 PM, Mauro Carvalho Chehab
<mchehab@s-opensource.com> wrote:
> Em Sat, 26 Aug 2017 15:50:02 +0530
> Bhumika Goyal <bhumirks@gmail.com> escreveu:
>
>> Make make video_device const.
>>
>> Bhumika Goyal (10):
>> [media] cx88: make video_device const
>> [media] dt3155: make video_device const
>> [media]: marvell-ccic: make video_device const
>> [media] mx2-emmaprp: make video_device const
>> [media]: s5p-g2d: make video_device const
>> [media]: ti-vpe: make video_device const
>> [media] via-camera: make video_device const
>> [media]: fsl-viu: make video_device const
>> [media] m2m-deinterlace: make video_device const
>> [media] vim2m: make video_device const
>>
>> drivers/media/pci/cx88/cx88-blackbird.c | 2 +-
>> drivers/media/pci/dt3155/dt3155.c | 2 +-
>> drivers/media/platform/fsl-viu.c | 2 +-
>> drivers/media/platform/m2m-deinterlace.c | 2 +-
>> drivers/media/platform/marvell-ccic/mcam-core.c | 2 +-
>> drivers/media/platform/mx2_emmaprp.c | 2 +-
>> drivers/media/platform/s5p-g2d/g2d.c | 2 +-
>> drivers/media/platform/ti-vpe/cal.c | 2 +-
>> drivers/media/platform/ti-vpe/vpe.c | 2 +-
>> drivers/media/platform/via-camera.c | 2 +-
>> drivers/media/platform/vim2m.c | 2 +-
>
> Please, don't do one such cleanup patch per file. Instead, group
> it per subdirectory, e. g. on e patch for:
> drivers/media/platform/
>
> and another one for:
> drivers/media/pci/
>
> That makes a lot easier to review and apply.
>
Okay, I will keep this in mind. Should I send a v2 for both the series?
Thanks,
Bhumika
> Thanks,
> Mauro
next prev parent reply other threads:[~2017-08-26 12:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-26 10:20 [PATCH 00/10] [media] platform: make video_device const Bhumika Goyal
2017-08-26 10:20 ` [PATCH 01/10] [media] cx88: " Bhumika Goyal
2017-08-26 10:20 ` [PATCH 02/10] [media] dt3155: " Bhumika Goyal
2017-08-26 10:20 ` [PATCH 03/10] [media]: marvell-ccic: " Bhumika Goyal
2017-08-26 10:20 ` [PATCH 04/10] [media] mx2-emmaprp: " Bhumika Goyal
2017-08-26 10:20 ` [PATCH 05/10] [media]: s5p-g2d: " Bhumika Goyal
2017-08-26 10:20 ` [PATCH 06/10] [media]: ti-vpe: " Bhumika Goyal
2017-08-26 10:20 ` [PATCH 07/10] [media] via-camera: " Bhumika Goyal
2017-08-26 10:20 ` [PATCH 08/10] [media]: fsl-viu: " Bhumika Goyal
2017-08-26 10:20 ` [PATCH 09/10] [media] m2m-deinterlace: " Bhumika Goyal
2017-08-26 10:20 ` [PATCH 10/10] [media] vim2m: " Bhumika Goyal
2017-08-26 11:59 ` [PATCH 00/10] [media] platform: " Mauro Carvalho Chehab
2017-08-26 12:12 ` Bhumika Goyal [this message]
2017-08-26 12:28 ` 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='CAOH+1jH0BUgoyJK7=QUQcBMpqYf+W0TeMyJ+T2JSyxzY2Ha8fQ@mail.gmail.com' \
--to=bhumirks@gmail.com \
--cc=a.hajda@samsung.com \
--cc=bparrot@ti.com \
--cc=corbet@lwn.net \
--cc=hverkuil@xs4all.nl \
--cc=julia.lawall@lip6.fr \
--cc=kamil@wypas.org \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=mchehab@s-opensource.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;
as well as URLs for NNTP newsgroup(s).