From: Chen-Yu Tsai <wens@csie.org>
To: Mauro Carvalho Chehab <mchehab@kernel.org>,
Maxime Ripard <maxime.ripard@bootlin.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
Jagan Teki <jagan@amarulasolutions.com>,
Rob Herring <robh@kernel.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>
Subject: Re: [git:media_tree/master] media: dt-bindings: media: sun6i: Separate H3 compatible from A31
Date: Thu, 17 Jan 2019 10:45:11 +0800 [thread overview]
Message-ID: <CAGb2v64nWOZ4ycEYZxUzZUXub9QLvdjdaojGdPeqjuO9hxih5Q@mail.gmail.com> (raw)
In-Reply-To: <E1gjq1q-0002RQ-B4@www.linuxtv.org>
Hi,
On Thu, Jan 17, 2019 at 2:35 AM Mauro Carvalho Chehab
<mchehab+samsung@kernel.org> wrote:
>
> This is an automatic generated email to let you know that the following patch were queued:
>
> Subject: media: dt-bindings: media: sun6i: Separate H3 compatible from A31
> Author: Chen-Yu Tsai <wens@csie.org>
> Date: Fri Nov 30 02:58:44 2018 -0500
>
> The CSI controller found on the H3 (and H5) is a reduced version of the
> one found on the A31. It only has 1 channel, instead of 4 channels for
> time-multiplexed BT.656. Since the H3 is a reduced version, it cannot
> "fallback" to a compatible that implements more features than it
> supports.
>
> Split out the H3 compatible as a separate entry, with no fallback.
>
> Fixes: b7eadaa3a02a ("media: dt-bindings: media: sun6i: Add A31 and H3 compatibles")
>
> Signed-off-by: Chen-Yu Tsai <wens@csie.org>
> Reviewed-by: Jagan Teki <jagan@amarulasolutions.com>
> Reviewed-by: Rob Herring <robh@kernel.org>
> Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
> Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
I see this is applied to the master branch, which I assume is -next material.
We'd prefer if this patch, and "media: sun6i: Add H3 compatible", were applied
as fixes for 5.0-rc. That way the bindings and drivers are fixed up in the same
release as they were introduced in, and we wouldn't be carrying an incorrect
binding, even if it were only for just one release.
Thanks
ChenYu
parent reply other threads:[~2019-01-17 2:45 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <E1gjq1q-0002RQ-B4@www.linuxtv.org>]
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=CAGb2v64nWOZ4ycEYZxUzZUXub9QLvdjdaojGdPeqjuO9hxih5Q@mail.gmail.com \
--to=wens@csie.org \
--cc=jagan@amarulasolutions.com \
--cc=linux-media@vger.kernel.org \
--cc=maxime.ripard@bootlin.com \
--cc=mchehab@kernel.org \
--cc=robh@kernel.org \
--cc=sakari.ailus@linux.intel.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).