From: Tzung-Bi Shih <tzungbi@kernel.org>
To: Mark Hasemeyer <markhas@chromium.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Raul Rangel <rrangel@chromium.org>,
Bhanu Prakash Maiya <bhanumaiya@chromium.org>,
kernel test robot <lkp@intel.com>,
Prashant Malani <pmalani@chromium.org>,
Benson Leung <bleung@chromium.org>,
Guenter Roeck <groeck@chromium.org>,
chrome-platform@lists.linux.dev
Subject: Re: [PATCH v12 1/3] platform/chrome: cros_ec_uart: Add cros-ec-uart transport layer
Date: Tue, 27 Dec 2022 18:16:11 +0800 [thread overview]
Message-ID: <Y6rF63MClDySamGs@google.com> (raw)
In-Reply-To: <20221209092619.v12.1.If7926fcbad397bc6990dd725690229bed403948c@changeid>
On Fri, Dec 09, 2022 at 09:26:22AM -0700, Mark Hasemeyer wrote:
[...]
> Reported-by: kernel test robot <lkp@intel.com>
Missed 1 comment from previous email. Please drop the tag as this patch
isn't a fix. The robot didn't report to add "cros-ec-uart".
One comment for the title "platform/chrome: cros_ec_uart: Add cros-ec-uart
transport layer". I think you could drop "cros-ec-uart" as the information
is duplicated.
next prev parent reply other threads:[~2022-12-27 10:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 16:26 [PATCH v12 1/3] platform/chrome: cros_ec_uart: Add cros-ec-uart transport layer Mark Hasemeyer
2022-12-09 16:26 ` [PATCH v12 2/3] dt-bindings: mfd: cros-ec: Add UART compatible string Mark Hasemeyer
2022-12-09 16:26 ` [PATCH v12 3/3] platform/chrome: cros_ec_uart: Add DT enumeration support Mark Hasemeyer
2022-12-26 8:12 ` [PATCH v12 1/3] platform/chrome: cros_ec_uart: Add cros-ec-uart transport layer Tzung-Bi Shih
2022-12-27 10:16 ` Tzung-Bi Shih [this message]
2022-12-28 3:50 ` patchwork-bot+chrome-platform
2022-12-28 5:40 ` patchwork-bot+chrome-platform
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=Y6rF63MClDySamGs@google.com \
--to=tzungbi@kernel.org \
--cc=bhanumaiya@chromium.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=groeck@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=markhas@chromium.org \
--cc=pmalani@chromium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.