From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Rob Herring <robh+dt@kernel.org>
Cc: Fabrizio Castro <fabrizio.castro.jz@renesas.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Ramesh Shanmugasundaram <rashanmu@gmail.com>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"open list:MEDIA DRIVERS FOR RENESAS - FCP"
<linux-renesas-soc@vger.kernel.org>,
devicetree@vger.kernel.org,
Chris Paterson <Chris.Paterson2@renesas.com>,
Biju Das <biju.das.jz@bp.renesas.com>,
Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: Re: [PATCH] media: dt-bindings: media: renesas,drif: Fix fck definition
Date: Sat, 5 Jun 2021 01:05:33 +0300 [thread overview]
Message-ID: <YLqjrdsJ8TKaiB1v@pendragon.ideasonboard.com> (raw)
In-Reply-To: <CAL_JsqJU6NGGtHUqfNrRqg5Km5n35LviUrazoU2dL82vB-+BvQ@mail.gmail.com>
Hi Rob,
On Fri, Jun 04, 2021 at 02:38:36PM -0500, Rob Herring wrote:
> On Tue, Apr 27, 2021 at 3:08 PM Laurent Pinchart wrote:
> > On Tue, Apr 27, 2021 at 01:02:57PM -0500, Rob Herring wrote:
> > > On Fri, Apr 9, 2021 at 1:54 PM Rob Herring wrote:
> > > > On Thu, 08 Apr 2021 21:24:36 +0100, Fabrizio Castro wrote:
> > > > > dt_binding_check reports the below error with the latest schema:
> > > > >
> > > > > Documentation/devicetree/bindings/media/renesas,drif.yaml:
> > > > > properties:clock-names:maxItems: False schema does not allow 1
> > > > > Documentation/devicetree/bindings/media/renesas,drif.yaml:
> > > > > ignoring, error in schema: properties: clock-names: maxItems
> > > > >
> > > > > This patch fixes the problem.
> > > > >
> > > > > Signed-off-by: Fabrizio Castro <fabrizio.castro.jz@renesas.com>
> > > > > ---
> > > > > Documentation/devicetree/bindings/media/renesas,drif.yaml | 4 +---
> > > > > 1 file changed, 1 insertion(+), 3 deletions(-)
> > > > >
> > > >
> > > > Reviewed-by: Rob Herring <robh@kernel.org>
> > >
> > > Still failing in linux-next...
> >
> > Sorry, as a standalone fix, I incorrectly thought you'd merge it.
> >
> > Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> >
> > and applied to my tree. I'll send a pull request to linux-media when the
> > merge window closes.
>
> Still failing in linux-next. It's also a failure in Linus' tree, so it
> needs to go in as a fix.
Sorry, been overwhelmed. Feel free to take the patch through your tree
as a fix.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2021-06-04 22:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-08 20:24 [PATCH] media: dt-bindings: media: renesas,drif: Fix fck definition Fabrizio Castro
2021-04-09 18:54 ` Rob Herring
2021-04-27 18:02 ` Rob Herring
2021-04-27 20:08 ` Laurent Pinchart
2021-06-04 19:38 ` Rob Herring
2021-06-04 22:05 ` Laurent Pinchart [this message]
2021-06-09 1:04 ` Rob Herring
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=YLqjrdsJ8TKaiB1v@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=Chris.Paterson2@renesas.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=fabrizio.castro.jz@renesas.com \
--cc=geert+renesas@glider.be \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=rashanmu@gmail.com \
--cc=robh+dt@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).