devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Jeff Chase <jnchase@google.com>
Cc: mchehab@kernel.org, robh+dt@kernel.org, hverkuil-cisco@xs4all.nl,
	linux-media@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v5 1/2] dt-bindings: Add ch7322 media i2c device
Date: Wed, 17 Jun 2020 14:26:45 -0600	[thread overview]
Message-ID: <20200617202645.GA2728573@bogus> (raw)
In-Reply-To: <20200615193811.233737-2-jnchase@google.com>

On Mon, 15 Jun 2020 15:38:10 -0400, Jeff Chase wrote:
> The ch7322 is a Chrontel CEC controller.
> 
> Signed-off-by: Jeff Chase <jnchase@google.com>
> ---
>  .../bindings/media/i2c/chrontel,ch7322.yaml   | 67 +++++++++++++++++++
>  MAINTAINERS                                   |  7 ++
>  2 files changed, 74 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/media/i2c/chrontel,ch7322.yaml
> 


Please add Acked-by/Reviewed-by tags when posting new versions. However,
there's no need to repost patches *only* to add the tags. The upstream
maintainer will do that for acks received on the version they apply.

If a tag was not added on purpose, please state why and what changed.


  reply	other threads:[~2020-06-17 20:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-15 19:38 [PATCH v5 0/2] CH7322 CEC controller driver Jeff Chase
2020-06-15 19:38 ` [PATCH v5 1/2] dt-bindings: Add ch7322 media i2c device Jeff Chase
2020-06-17 20:26   ` Rob Herring [this message]
2020-06-17 22:07     ` Jeff Chase
2020-06-15 19:38 ` [PATCH v5 2/2] media: cec: i2c: ch7322: Add ch7322 CEC controller driver Jeff Chase
2020-06-18  7:51   ` Hans Verkuil
2020-06-18  8:59     ` Jeff Chase
2020-06-18 10:05       ` Hans Verkuil
2020-06-18 16:25         ` Jeff Chase
2020-06-18 16:33           ` Hans Verkuil
2020-06-18 16:40             ` Jeff Chase
2020-06-20  4:56               ` Jeff Chase
2020-06-20  8:57                 ` Hans Verkuil

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=20200617202645.GA2728573@bogus \
    --to=robh@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=hverkuil-cisco@xs4all.nl \
    --cc=jnchase@google.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).