From: Lee Jones <lee@kernel.org>
To: Mark Hasemeyer <markhas@chromium.org>
Cc: Tzung-Bi Shih <tzungbi@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Raul Rangel <rrangel@chromium.org>,
Bhanu Prakash Maiya <bhanumaiya@chromium.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Benson Leung <bleung@chromium.org>,
Guenter Roeck <groeck@chromium.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.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: Tue, 10 Jan 2023 10:24:38 +0000 [thread overview]
Message-ID: <Y7085l4J0jbrkd6G@google.com> (raw)
In-Reply-To: <CANg-bXDrSJCGk27YKheupm9YND1fSaBaYfQ1Bd-4C-PnH67ioQ@mail.gmail.com>
On Mon, 09 Jan 2023, Mark Hasemeyer wrote:
> On Wed, Jan 4, 2023 at 9:08 AM Lee Jones <lee@kernel.org> wrote:
> > I changed the subject line and applied the patch, thanks.
>
> Hey Lee, a couple comments/questions:
> 1. The subject line of this patch was updated in v11 of the series.
> 2. What tree was the patch applied to? I don't see the changes in linux-next.
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/Documentation/devicetree/bindings/mfd/google,cros-ec.yaml
Thanks for flagging. You will do tomorrow.
--
Lee Jones [李琼斯]
prev parent reply other threads:[~2023-01-10 10:25 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
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 [this message]
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=Y7085l4J0jbrkd6G@google.com \
--to=lee@kernel.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=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markhas@chromium.org \
--cc=robh+dt@kernel.org \
--cc=rrangel@chromium.org \
--cc=tzungbi@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).