linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jiri Kosina <jikos@kernel.org>,
	Benjamin Tissoires <benjamin.tissoires@redhat.com>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Jason Gerecke <jason.gerecke@wacom.com>
Subject: linux-next: Fixes tag needs some work in the hid tree
Date: Tue, 20 Aug 2019 01:19:04 +1000	[thread overview]
Message-ID: <20190820011904.34962638@canb.auug.org.au> (raw)

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

Hi all,

In commit

  b72fb1dcd2ea ("HID: wacom: Correct distance scale for 2nd-gen Intuos devices")

Fixes tag

  Fixes: eda01dab53 ("HID: wacom: Add four new Intuos devices")

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

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2019-08-19 15:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-19 15:19 Stephen Rothwell [this message]
2019-11-06 20:56 linux-next: Fixes tag needs some work in the hid tree Stephen Rothwell
2020-02-12 20:49 Stephen Rothwell
2020-02-13  6:28 ` Johan Korsnes (jkorsnes)
2020-04-29 22:06 Stephen Rothwell
2020-05-01 16:56 ` Jason Gerecke
2020-10-29 20:58 Stephen Rothwell
2021-05-05 22:21 Stephen Rothwell
2021-11-22 21:17 Stephen Rothwell
2021-11-22 22:59 ` Thomas Weißschuh
2022-03-14 11:09 Stephen Rothwell
2022-07-24 22:04 Stephen Rothwell
2022-08-25 23:56 Stephen Rothwell
2022-08-28 10:14 ` José Expósito
2023-01-26 22:39 Stephen Rothwell
2024-02-13 21:07 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=20190820011904.34962638@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=benjamin.tissoires@redhat.com \
    --cc=jason.gerecke@wacom.com \
    --cc=jikos@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).