From: Maxime Ripard <mripard@kernel.org>
To: Sean Young <sean@mess.org>
Cc: mchehab@kernel.org, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org, Chen-Yu Tsai <wens@csie.org>,
Mark Rutland <mark.rutland@arm.com>,
Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
Rob Herring <robh@kernel.org>
Subject: Re: [PATCH v2 1/2] dt-bindings: media: Add YAML schemas for the generic RC bindings
Date: Tue, 20 Aug 2019 11:50:28 +0200 [thread overview]
Message-ID: <20190820095028.l74sfvipwjjla6kq@flea> (raw)
In-Reply-To: <20190820081525.celdosrgcvwoq6e7@gofer.mess.org>
[-- Attachment #1: Type: text/plain, Size: 677 bytes --]
Hi Sean,
On Tue, Aug 20, 2019 at 09:15:26AM +0100, Sean Young wrote:
> On Mon, Aug 19, 2019 at 08:26:18PM +0200, Maxime Ripard wrote:
> > From: Maxime Ripard <maxime.ripard@bootlin.com>
> >
> > The RC controllers have a bunch of generic properties that are needed in a
> > device tree. Add a YAML schemas for those.
> >
> > Reviewed-by: Rob Herring <robh@kernel.org>
> > Signed-off-by: Maxime Ripard <maxime.ripard@bootlin.com>
>
> For the series (both 1/2 and 2.2):
>
> Reviewed-by: Sean Young <sean@mess.org>
>
> How's tree should this go through?
Either yours or Rob's, I guess?
Maxime
--
Maxime Ripard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2019-08-20 9:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-19 18:26 [PATCH v2 1/2] dt-bindings: media: Add YAML schemas for the generic RC bindings Maxime Ripard
2019-08-19 18:26 ` [PATCH v2 2/2] dt-bindings: media: Convert Allwinner A10 IR to a schema Maxime Ripard
2019-08-20 8:15 ` [PATCH v2 1/2] dt-bindings: media: Add YAML schemas for the generic RC bindings Sean Young
2019-08-20 9:50 ` Maxime Ripard [this message]
2019-08-20 15:52 ` Rob Herring
2019-08-20 16:22 ` Sean Young
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=20190820095028.l74sfvipwjjla6kq@flea \
--to=mripard@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mchehab@kernel.org \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=sean@mess.org \
--cc=wens@csie.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;
as well as URLs for NNTP newsgroup(s).