From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Yoshihiro Kaneko <ykaneko0929@gmail.com>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Simon Horman <horms@verge.net.au>,
Magnus Damm <magnus.damm@gmail.com>,
Linux-sh list <linux-sh@vger.kernel.org>
Subject: Re: [PATCH v3] media: soc_camera: rcar_vin: Add rcar fallback compatibility string
Date: Mon, 25 Jan 2016 08:57:40 +0000 [thread overview]
Message-ID: <CAMuHMdUFWdfHrpCwkuDUTmdBUNdt2d=QZ8hKBbh5CF9wnFdtRA@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1601231834370.10701@axis700.grange>
Hi Guennadi,
On Sat, Jan 23, 2016 at 6:37 PM, Guennadi Liakhovetski
<g.liakhovetski@gmx.de> wrote:
> On Thu, 14 Jan 2016, Yoshihiro Kaneko wrote:
>> Add fallback compatibility string for R-Car Gen2 and Gen3, This is
>> in keeping with the fallback scheme being adopted wherever appropriate
>> for drivers for Renesas SoCs.
>>
>> Signed-off-by: Yoshihiro Kaneko <ykaneko0929@gmail.com>
>> ---
>>
>> This patch is based on the for-4.6-1 branch of Guennadi's v4l-dvb tree.
>>
>> v3 [Yoshihiro Kaneko]
>> * rebased to for-4.6-1 branch of Guennadi's tree.
>>
>> v2 [Yoshihiro Kaneko]
>> * As suggested by Geert Uytterhoeven
>> drivers/media/platform/soc_camera/rcar_vin.c:
>> - The generic compatibility values are listed at the end of the
>> rcar_vin_of_table[].
>>
>> Documentation/devicetree/bindings/media/rcar_vin.txt | 8 +++++++-
>> drivers/media/platform/soc_camera/rcar_vin.c | 2 ++
>
> I might be wrong in this specific case, please, correct me someone, but
> doesn't Documentation/devicetree/bindings/submitting-patches.txt tell us
> to submit bindings patches separately from the drivers part?
I think that mostly applies to new bindings and new drivers.
For small updates (e.g. adding a new compatible value), these tend to be
submitted as a single patch.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
prev parent reply other threads:[~2016-01-25 8:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-13 17:58 [PATCH v3] media: soc_camera: rcar_vin: Add rcar fallback compatibility string Yoshihiro Kaneko
2016-01-13 17:59 ` [PATCH v3] media: soc_camera: rcar_vin: Add ARGB8888 caputre format support Yoshihiro Kaneko
2016-01-13 18:27 ` Sergei Shtylyov
2016-01-13 18:18 ` kbuild test robot
2016-01-23 17:37 ` [PATCH v3] media: soc_camera: rcar_vin: Add rcar fallback compatibility string Guennadi Liakhovetski
2016-01-25 8:57 ` Geert Uytterhoeven [this message]
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='CAMuHMdUFWdfHrpCwkuDUTmdBUNdt2d=QZ8hKBbh5CF9wnFdtRA@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=g.liakhovetski@gmx.de \
--cc=horms@verge.net.au \
--cc=linux-media@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=ykaneko0929@gmail.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).