All of lore.kernel.org
 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: Zhengping Jiang <jiangzp@google.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: Mon, 25 Jul 2022 07:53:50 +1000	[thread overview]
Message-ID: <20220725075350.64662d13@canb.auug.org.au> (raw)

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

Hi all,

In commit

  68253f3cd715 ("Bluetooth: hci_sync: Fix resuming scan after suspend resume")

Fixes tag

  Fixes: 3b42055388c30 (Bluetooth: hci_sync: Fix attempting to suspend with

has these problem(s):

  - Subject has leading but no trailing parentheses

Please do not split Fixes tags over more than one line, just use:

  git log -1 --format='Fixes: %h ("%s")' <commit>

Also, please keep all the commit message tags together at the end of
the commit message.

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2022-07-24 22:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-24 21:53 Stephen Rothwell [this message]
2022-07-24 21:59 ` linux-next: Fixes tag needs some work in the bluetooth tree Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2024-04-30 21:50 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-12 22:48 Stephen Rothwell
2022-01-06 21:19 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=20220725075350.64662d13@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=jiangzp@google.com \
    --cc=johan.hedberg@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 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.