public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Rob Herring <robh@kernel.org>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	Dave Stevenson <dave.stevenson@raspberrypi.com>,
	Jacopo Mondi <jacopo@jmondi.org>,
	"Paul J. Murphy" <paul.j.murphy@intel.com>,
	Daniele Alessandrelli <daniele.alessandrelli@intel.com>,
	Krzysztof Kozlowski <krzk@kernel.org>,
	Paul Kocialkowski <paul.kocialkowski@bootlin.com>,
	linux-media@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: media: Use graph and video-interfaces schemas, round 2
Date: Tue, 23 Feb 2021 23:22:29 +0200	[thread overview]
Message-ID: <20210223212229.GI3@paasikivi.fi.intel.com> (raw)
In-Reply-To: <20210223210127.55455-1-robh@kernel.org>

Hi Rob,

On Tue, Feb 23, 2021 at 03:01:27PM -0600, Rob Herring wrote:
> A couple of media schemas got applied without using or incorrectly
> using the video-interfaces.yaml and graph.yaml schemas. Fix them up
> before we have more copy-n-paste errors.
> 
> Fixes: 41b3e23376e9 ("media: dt-bindings: media: Add bindings for imx334")
> Fixes: d899e5f1db7a ("media: dt-bindings: media: imx258: add bindings for IMX258 sensor")
> Fixes: 918b866edfec ("media: dt-bindings: Remove old ov5647.yaml file, update ovti,ov5647.yaml")
> Fixes: 22f2b47517a6 ("media: dt-bindings: media: i2c: Add OV8865 bindings documentation")
> Fixes: 29a202fa7acc ("media: dt-bindings: media: i2c: Add OV5648 bindings documentation")
> Cc: Sakari Ailus <sakari.ailus@linux.intel.com>
> Cc: Mauro Carvalho Chehab <mchehab@kernel.org>
> Cc: Dave Stevenson <dave.stevenson@raspberrypi.com>
> Cc: Jacopo Mondi <jacopo@jmondi.org>
> Cc: "Paul J. Murphy" <paul.j.murphy@intel.com>
> Cc: Daniele Alessandrelli <daniele.alessandrelli@intel.com>
> Cc: Krzysztof Kozlowski <krzk@kernel.org>
> Cc: Paul Kocialkowski <paul.kocialkowski@bootlin.com>
> Cc: linux-media@vger.kernel.org
> Signed-off-by: Rob Herring <robh@kernel.org>
> ---
> Please ack and I'll send to Linus for rc1.
> 
>  .../devicetree/bindings/media/i2c/imx258.yaml    | 14 +++++++-------
>  .../bindings/media/i2c/ovti,ov5647.yaml          |  5 ++---
>  .../bindings/media/i2c/ovti,ov5648.yaml          | 16 +++++-----------
>  .../bindings/media/i2c/ovti,ov8865.yaml          | 16 +++++-----------
>  .../bindings/media/i2c/sony,imx334.yaml          | 11 +++++------
>  5 files changed, 24 insertions(+), 38 deletions(-)

Thanks for addressing this.

Acked-by: Sakari Ailus <sakari.ailus@linux.intel.com>

-- 
Kind regards,

Sakari Ailus

  reply	other threads:[~2021-02-23 21:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-23 21:01 [PATCH] dt-bindings: media: Use graph and video-interfaces schemas, round 2 Rob Herring
2021-02-23 21:22 ` Sakari Ailus [this message]
2021-02-24 14:32 ` Krzysztof Kozlowski

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=20210223212229.GI3@paasikivi.fi.intel.com \
    --to=sakari.ailus@linux.intel.com \
    --cc=daniele.alessandrelli@intel.com \
    --cc=dave.stevenson@raspberrypi.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jacopo@jmondi.org \
    --cc=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=paul.j.murphy@intel.com \
    --cc=paul.kocialkowski@bootlin.com \
    --cc=robh@kernel.org \
    /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