public inbox for chrome-platform@lists.linux.dev
 help / color / mirror / Atom feed
From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Tzung-Bi Shih <tzungbi@kernel.org>
Cc: Jonathan Cameron <jic23@kernel.org>,
	Yiyuan Guo <yguoaz@gmail.com>, <lars@metafoo.de>,
	<bleung@chromium.org>, <groeck@google.com>,
	<dianders@chromium.org>, <mazziesaccount@gmail.com>,
	<gwendal@chromium.org>, <linux-iio@vger.kernel.org>,
	<chrome-platform@lists.linux.dev>
Subject: Re: [PATCH v3] iio: cros_ec: Fix the allocation size for cros_ec_command
Date: Tue, 18 Jul 2023 10:37:02 +0100	[thread overview]
Message-ID: <20230718103702.0000546e@Huawei.com> (raw)
In-Reply-To: <ZLSw1FxccNOqE52C@google.com>

On Mon, 17 Jul 2023 11:09:08 +0800
Tzung-Bi Shih <tzungbi@kernel.org> wrote:

> On Sun, Jul 16, 2023 at 02:10:28PM +0100, Jonathan Cameron wrote:
> [...]
> > 2) Various people commented on earlier versions, and I'm waiting for them to confirm
> > they are fine with this version.  
> 
> The version addressed all my comments and LGTM.

Tag?  I can pick up without, but it's nice to record this
formally.   Reviewed-by seems appropriate here.

  reply	other threads:[~2023-07-18  9:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-30 14:37 [PATCH v3] iio: cros_ec: Fix the allocation size for cros_ec_command Yiyuan Guo
2023-07-16 13:10 ` Jonathan Cameron
2023-07-16 13:55   ` yguoaz
2023-07-17  3:09   ` Tzung-Bi Shih
2023-07-18  9:37     ` Jonathan Cameron [this message]
2023-07-29 11:21       ` Jonathan Cameron
2023-09-11  4:31 ` patchwork-bot+chrome-platform
2023-09-11  4:49 ` patchwork-bot+chrome-platform
  -- strict thread matches above, loose matches on Subject: below --
2023-06-30  7:36 [PATCH v2] " Tzung-Bi Shih
2023-06-30  8:31 ` [PATCH v3] " Yiyuan Guo
2023-06-30 14:06   ` Guenter Roeck
2023-06-30 14:42     ` yguoaz

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=20230718103702.0000546e@Huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=bleung@chromium.org \
    --cc=chrome-platform@lists.linux.dev \
    --cc=dianders@chromium.org \
    --cc=groeck@google.com \
    --cc=gwendal@chromium.org \
    --cc=jic23@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=mazziesaccount@gmail.com \
    --cc=tzungbi@kernel.org \
    --cc=yguoaz@gmail.com \
    /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