Linux-Next Archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Marcel Holtmann <marcel@holtmann.org>,
	Johan Hedberg <johan.hedberg@gmail.com>
Cc: Miaoqian Lin <linmq006@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: Fixes tag needs some work in the bluetooth tree
Date: Fri, 7 Jan 2022 08:19:55 +1100	[thread overview]
Message-ID: <20220107081955.3b003103@canb.auug.org.au> (raw)

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

Hi all,

In commit

  6845667146a2 ("Bluetooth: hci_qca: Fix NULL vs IS_ERR_OR_NULL check in qca_serdev_probe")

Fixes tag

  Fixes: 77131dfe ("Bluetooth: hci_qca: Replace devm_gpiod_get() with devm_gpiod_get_optional()")

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:[~2022-01-06 21:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-06 21:19 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-04-30 21:50 linux-next: Fixes tag needs some work in the bluetooth tree Stephen Rothwell
2024-04-30 22:24 ` Sungwoo Kim
2022-11-09 17:39 Stephen Rothwell
2022-08-31 23:35 Stephen Rothwell
2022-07-24 21:53 Stephen Rothwell
2022-07-24 21:59 ` Stephen Rothwell
2022-07-12 22:48 Stephen Rothwell
2021-05-08  2:13 Stephen Rothwell
2020-10-01 11:53 Stephen Rothwell
2020-10-01 19:39 ` Anant Thazhemadam
2020-07-28 12:24 Stephen Rothwell
2020-05-29 12:14 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=20220107081955.3b003103@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=johan.hedberg@gmail.com \
    --cc=linmq006@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=marcel@holtmann.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 read-only IMAP folder(s) and NNTP newsgroup(s).