All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benson Leung <bleung@google.com>
To: Gwendal Grignou <gwendal@chromium.org>,
	enric.balletbo@collabora.com, groeck@chromium.org
Cc: linux-kernel@vger.kernel.org, bleung@chromium.org
Subject: Re: [PATCH] platform/chrome: cros_ec_trace: Fix format warnings
Date: Mon, 30 Aug 2021 17:29:45 -0700	[thread overview]
Message-ID: <YS13+XuZxGP2xAnZ@google.com> (raw)
In-Reply-To: <163036877941.809543.752509524579579884.b4-ty@chromium.org>

[-- Attachment #1: Type: text/plain, Size: 867 bytes --]

Hi Gwendal,

On Mon, Aug 30, 2021 at 05:13:54PM -0700, Benson Leung wrote:
> Hi Gwendal,
> 
> On Mon, 23 Aug 2021 13:01:32 -0700, Gwendal Grignou wrote:
> > Fix printf format issues in new tracing events.
> > 
> > Fixes: 814318242 ("platform/chrome: cros_ec_trace: Add fields to command traces")
> 
> Applied, thanks!
> 
> [1/1] platform/chrome: cros_ec_trace: Fix format warnings
>       commit: 5a51bdb0ae26cac8764bfb59839a34ea13155a47
> 
> Best regards,
> -- 
> Benson Leung
> Staff Software Engineer
> Chrome OS Kernel
> Google Inc.
> bleung@google.com
> Chromium OS Project
> bleung@chromium.org

Sorry about this, I merged v1 incorrectly, so I've repushed v3. Disregard this
thank you.

Benson

-- 
Benson Leung
Staff Software Engineer
Chrome OS Kernel
Google Inc.
bleung@google.com
Chromium OS Project
bleung@chromium.org

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      reply	other threads:[~2021-08-31  0:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-23 20:01 [PATCH] platform/chrome: cros_ec_trace: Fix format warnings Gwendal Grignou
2021-08-25 15:00 ` Guenter Roeck
2021-08-31  0:13 ` Benson Leung
2021-08-31  0:29   ` Benson Leung [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=YS13+XuZxGP2xAnZ@google.com \
    --to=bleung@google.com \
    --cc=bleung@chromium.org \
    --cc=enric.balletbo@collabora.com \
    --cc=groeck@chromium.org \
    --cc=gwendal@chromium.org \
    --cc=linux-kernel@vger.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 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.