From: Rob Herring <robh@kernel.org>
To: Bhanu Prakash Maiya <bhanumaiya@chromium.org>
Cc: linux-arm-kernel@lists.infradead.org,
Lee Jones <lee.jones@linaro.org>,
Furquan Shaikh <furquan@chromium.org>,
Raul E Rangel <rrangel@chromium.org>,
Eric Peers <epeers@google.com>,
Duncan Laurie <dlaurie@google.com>,
Benson Leung <bleung@chromium.org>,
Enric Balletbo i Serra <enric.balletbo@collabora.com>,
Guenter Roeck <groeck@chromium.org>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
"David S . Miller" <davem@davemloft.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
devicetree@vger.kernel.org, linux-kernel@vger.Kernel.org
Subject: Re: [PATCH v3 2/2] dt-bindings: mfd: Add DT compatible string "google,cros_ec_uart"
Date: Thu, 16 Jul 2020 13:13:18 -0600 [thread overview]
Message-ID: <20200716191318.GA2683551@bogus> (raw)
In-Reply-To: <20200715221150.v3.2.I113cdbaf66d48b37ac0faefb9b845480d122f3b9@changeid>
On Wed, Jul 15, 2020 at 10:16:04PM -0700, Bhanu Prakash Maiya wrote:
> From: Bhanu Prakash Maiya <bhanumaiya@chromium.org>
>
> Add DT compatible string in
> Documentation/devicetree/bindings/mfd/cros_ec.txt
Need to update this.
With that,
Reviewed-by: Rob Herring <robh@kernel.org>
> Signed-off-by: Bhanu Prakash Maiya <bhanumaiya@chromium.org>
> ---
>
> Changes in v3:
> - Rebased changes on google,cros-ec.yaml
>
> Changes in v2:
> - No change
>
> Documentation/devicetree/bindings/mfd/google,cros-ec.yaml | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
next prev parent reply other threads:[~2020-07-16 19:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-16 5:16 [PATCH v3 2/2] dt-bindings: mfd: Add DT compatible string "google,cros_ec_uart" Bhanu Prakash Maiya
2020-07-16 19:13 ` Rob Herring [this message]
2020-07-17 9:53 ` Enric Balletbo i Serra
2020-07-17 19:02 ` 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=20200716191318.GA2683551@bogus \
--to=robh@kernel.org \
--cc=bhanumaiya@chromium.org \
--cc=bleung@chromium.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=dlaurie@google.com \
--cc=enric.balletbo@collabora.com \
--cc=epeers@google.com \
--cc=furquan@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=groeck@chromium.org \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.Kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=rrangel@chromium.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).