From: Benson Leung <bleung@google.com>
To: Stephen Rothwell <sfr@rothwell.id.au>
Cc: Guenter Roeck <groeck@chromium.org>,
Enric Balletbo i Serra <enric.balletbo@collabora.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Gwendal Grignou <gwendal@chromium.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the chrome-platform tree
Date: Mon, 30 Aug 2021 17:17:45 -0700 [thread overview]
Message-ID: <YS11KS/XAGgTM5iQ@google.com> (raw)
In-Reply-To: <20210830172132.4fc0ae7f@elm.ozlabs.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 602 bytes --]
Hi Stephen,
On Mon, Aug 30, 2021 at 05:21:32PM +1000, Stephen Rothwell wrote:
> > Introduced by commit
> >
> > d453ceb6549a ("platform/chrome: sensorhub: Add trace events for sample")
>
> I am still seeing these warnings.
> --
> Cheers,
> Stephen Rothwell
I've just pushed this to chrome-platform's for-next:
5a51bdb0ae26 ("platform/chrome: cros_ec_trace: Fix format warnings")
This should fix those warnings. Sorry for the long delay.
--
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 --]
next prev parent reply other threads:[~2021-08-31 0:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-23 5:21 linux-next: build warning after merge of the chrome-platform tree Stephen Rothwell
2021-08-30 7:21 ` Stephen Rothwell
2021-08-31 0:17 ` Benson Leung [this message]
2021-08-31 0:32 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2024-06-03 3:25 Stephen Rothwell
2024-06-03 4:20 ` Tzung-Bi Shih
2022-05-16 11:38 Stephen Rothwell
2022-05-17 13:09 ` Muhammad Usama Anjum
2022-05-18 3:23 ` Bagas Sanjaya
2022-05-18 3:39 ` Tzung-Bi Shih
2022-05-18 4:24 ` Muhammad Usama Anjum
2019-04-16 4:30 Stephen Rothwell
2019-04-16 9:09 ` Enric Balletbo i Serra
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=YS11KS/XAGgTM5iQ@google.com \
--to=bleung@google.com \
--cc=dmitry.torokhov@gmail.com \
--cc=enric.balletbo@collabora.com \
--cc=groeck@chromium.org \
--cc=gwendal@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@rothwell.id.au \
/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.