From: "José Expósito" <jose.exposito89@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Jiri Kosina <jikos@kernel.org>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
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 hid tree
Date: Sun, 28 Aug 2022 12:14:50 +0200 [thread overview]
Message-ID: <20220828101450.GA183368@elementary> (raw)
In-Reply-To: <20220826095647.2484954f@canb.auug.org.au>
Hi,
On Fri, Aug 26, 2022 at 09:56:47AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> 609174edeb75 ("HID: uclogic: Fix warning in uclogic_rdesc_template_apply")
>
> Fixes tag
>
> Fixes: 08177f4 ("HID: uclogic: merge hid-huion driver in hid-uclogic")
Sorry about that, checkpatch didn't catch this one. This should read:
Fixes: 08177f40bd00 ("HID: uclogic: merge hid-huion driver in hid-uclogic")
> has these problem(s):
>
> - SHA1 should be at least 12 digits long
> This can be fixed for the future 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
next prev parent reply other threads:[~2022-08-28 10:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-25 23:56 linux-next: Fixes tag needs some work in the hid tree Stephen Rothwell
2022-08-28 10:14 ` José Expósito [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-27 21:05 Stephen Rothwell
2024-06-06 21:47 Stephen Rothwell
2024-06-07 9:12 ` Benjamin Tissoires
2024-05-07 21:35 Stephen Rothwell
2024-05-08 7:10 ` Kenny Levinsen
2024-02-13 21:07 Stephen Rothwell
2023-01-26 22:39 Stephen Rothwell
2022-07-24 22:04 Stephen Rothwell
2022-03-14 11:09 Stephen Rothwell
2021-11-22 21:17 Stephen Rothwell
2021-11-22 22:59 ` Thomas Weißschuh
2021-05-05 22:21 Stephen Rothwell
2020-10-29 20:58 Stephen Rothwell
2020-04-29 22:06 Stephen Rothwell
2020-05-01 16:56 ` Jason Gerecke
2020-02-12 20:49 Stephen Rothwell
2020-02-13 6:28 ` Johan Korsnes (jkorsnes)
2019-11-06 20:56 Stephen Rothwell
2019-08-19 15:19 Stephen Rothwell
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=20220828101450.GA183368@elementary \
--to=jose.exposito89@gmail.com \
--cc=benjamin.tissoires@redhat.com \
--cc=jikos@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox