From: Mauro Carvalho Chehab <mchehab@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: Sakari Ailus <sakari.ailus@linux.intel.com>,
Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
devicetree@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
Guennadi Liakhovetski <guennadi.liakhovetski@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Jacopo Mondi <jacopo@jmondi.org>
Subject: Re: [PATCH v4 1/2] media: dt-bindings: Convert video-interfaces.txt properties to schemas
Date: Fri, 22 Jan 2021 22:43:03 +0100 [thread overview]
Message-ID: <20210122224303.6a743c83@coco.lan> (raw)
In-Reply-To: <20210122170144.GE27155@paasikivi.fi.intel.com>
Em Fri, 22 Jan 2021 19:01:44 +0200
Sakari Ailus <sakari.ailus@linux.intel.com> escreveu:
> Hi Rob,
>
> On Fri, Jan 22, 2021 at 10:23:44AM -0600, Rob Herring wrote:
> > On Mon, Jan 4, 2021 at 10:58 AM Rob Herring <robh@kernel.org> wrote:
> > >
> > > Convert video-interfaces.txt to DT schema. As it contains a mixture of
> > > device level and endpoint properties, split it up into 2 schemas.
> >
> > Ping!
> >
> > Can this please be applied to the media tree so I can tell folks to
> > use it in reviews of media bindings.
Just merged both patches.
> Yes, it can. It's in my tree now.
Thanks,
Mauro
next prev parent reply other threads:[~2021-01-22 21:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 16:58 [PATCH v4 0/2] dt-bindings: media: Convert video-interfaces.txt to schemas Rob Herring
2021-01-04 16:58 ` [PATCH v4 1/2] media: dt-bindings: Convert video-interfaces.txt properties " Rob Herring
2021-01-22 16:23 ` Rob Herring
2021-01-22 17:01 ` Sakari Ailus
2021-01-22 21:43 ` Mauro Carvalho Chehab [this message]
2021-01-04 16:58 ` [PATCH v4 2/2] dt-bindings: media: Use graph and video-interfaces schemas Rob Herring
2021-01-05 4:59 ` Laurent Pinchart
2021-01-05 8:59 ` Maxime Ripard
2021-01-05 9:09 ` Sakari Ailus
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=20210122224303.6a743c83@coco.lan \
--to=mchehab@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=g.liakhovetski@gmx.de \
--cc=guennadi.liakhovetski@linux.intel.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=jacopo@jmondi.org \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mripard@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).