From: Benson Leung <bleung@google.com>
To: Stephen Rothwell <sfr@canb.auug.org.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: Fixes tag needs some work in the chrome-platform tree
Date: Mon, 30 Aug 2021 17:48:36 -0700 [thread overview]
Message-ID: <YS18ZIR7+DctTlCH@google.com> (raw)
In-Reply-To: <20210831103906.5c590f67@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 847 bytes --]
Hi Stephen,
On Tue, Aug 31, 2021 at 10:39:06AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> cf7f3ebb41d8 ("platform/chrome: cros_ec_trace: Fix format warnings")
>
> Fixes tag
>
> Fixes: 814318242 ("platform/chrome: cros_ec_trace: Add fields to command traces")
>
> has these problem(s):
>
> - SHA1 should be at least 12 digits long
> Can be fixed by setting core.abbrev to 12 (or more) or (for git v2.11
> or later) just making sure it is not set (or set to "auto").
>
> --
> Cheers,
> Stephen Rothwell
Sorry about all the churn. One last time, my for-next has been updated:
4665584888ad ("platform/chrome: cros_ec_trace: Fix format warnings")
--
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:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-31 0:39 linux-next: Fixes tag needs some work in the chrome-platform tree Stephen Rothwell
2021-08-31 0:48 ` Benson Leung [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-03-31 20:58 Stephen Rothwell
2020-03-29 21:19 Stephen Rothwell
2020-03-30 6:27 ` Enric Balletbo 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=YS18ZIR7+DctTlCH@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@canb.auug.org.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.