From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Mark Hasemeyer <markhas@chromium.org>,
LKML <linux-kernel@vger.kernel.org>
Cc: Raul Rangel <rrangel@chromium.org>,
Bhanu Prakash Maiya <bhanumaiya@chromium.org>,
Benson Leung <bleung@chromium.org>,
Guenter Roeck <groeck@chromium.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Lee Jones <lee@kernel.org>, Rob Herring <robh+dt@kernel.org>,
chrome-platform@lists.linux.dev, devicetree@vger.kernel.org
Subject: Re: [PATCH v10 2/3] dt-bindings: mfd: Add compatible string for UART support
Date: Wed, 7 Dec 2022 18:57:37 +0100 [thread overview]
Message-ID: <185a83f7-d575-245c-8d11-1de7c8064a7f@linaro.org> (raw)
In-Reply-To: <20221207104005.v10.2.I9e018ecb8bdf341648cb64417085978ff0d22a46@changeid>
On 07/12/2022 18:40, Mark Hasemeyer wrote:
> From: Bhanu Prakash Maiya <bhanumaiya@chromium.org>
>
> Add a compatible string to support the UART implementation of the cros
> ec interface. The driver does not support the reg and interrupt
> properties, so exempt them from being required for UART compatible nodes.
>
> Signed-off-by: Bhanu Prakash Maiya <bhanumaiya@chromium.org>
> Co-developed-by: Mark Hasemeyer <markhas@chromium.org>
> Signed-off-by: Mark Hasemeyer <markhas@chromium.org>
> Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Use subject prefixes matching the subsystem (git log --oneline -- ...)
and device. Currently it looks like you change ENTIRE MFD subsystem.
> ---
>
> Changes in v10:
> - No change
>
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-12-07 17:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221207104005.v10.1.If7926fcbad397bc6990dd725690229bed403948c@changeid>
2022-12-07 17:40 ` [PATCH v10 2/3] dt-bindings: mfd: Add compatible string for UART support Mark Hasemeyer
2022-12-07 17:57 ` Krzysztof Kozlowski [this message]
2023-01-04 16:08 ` Lee Jones
2023-01-05 1:10 ` Tzung-Bi Shih
2023-01-05 14:13 ` Lee Jones
2023-01-05 14:24 ` Lee Jones
2023-01-05 15:35 ` Tzung-Bi Shih
2023-01-05 16:27 ` Lee Jones
2023-01-05 18:08 ` Tzung-Bi Shih
2023-01-09 19:06 ` Mark Hasemeyer
2023-01-10 10:24 ` Lee Jones
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=185a83f7-d575-245c-8d11-1de7c8064a7f@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=bhanumaiya@chromium.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=devicetree@vger.kernel.org \
--cc=groeck@chromium.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markhas@chromium.org \
--cc=robh+dt@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).