public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Mark Brown <broonie@kernel•org>, Liam Girdwood <lgirdwood@gmail•com>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Ranjani Sridharan <ranjani.sridharan@linux•intel.com>
Subject: linux-next: Fixes tag needs some work in the sound-asoc-fixes tree
Date: Thu, 11 Apr 2019 07:00:30 +1000	[thread overview]
Message-ID: <20190411070020.38749a8b@canb.auug.org.au> (raw)

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

Hi all,

In commit

  70802487bb91 ("ASoC: pcm: fix error handling when try_module_get() fails.")

Fixes tag

  Fixes: 52034add7 (ASoC: pcm: update module refcount if

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").
  - 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>

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2019-04-10 21:00 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-10 21:00 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-31 21:06 linux-next: Fixes tag needs some work in the sound-asoc-fixes tree Stephen Rothwell
2021-12-16 13:00 Stephen Rothwell
2021-11-14  7:23 Stephen Rothwell
2021-06-01 22:00 Stephen Rothwell
2020-05-13 21:12 Stephen Rothwell
2020-05-13 21:20 ` Dan Murphy
2020-05-14 10:04   ` Mark Brown
2020-04-28 21:59 Stephen Rothwell
2020-04-14 22:00 Stephen Rothwell
2020-03-12 20:39 Stephen Rothwell
2020-03-01  5:38 Stephen Rothwell
2020-02-19  3:14 Stephen Rothwell
2020-01-19  1:13 Stephen Rothwell
2019-10-01 22:29 Stephen Rothwell
2019-10-02  7:55 ` Kai Vehmanen
2019-06-10 18:41 Stephen Rothwell
2019-06-06 22:01 Stephen Rothwell
2019-05-13 15:00 Stephen Rothwell
2019-02-26 20:42 Stephen Rothwell
2019-02-07 20:31 Stephen Rothwell
2019-02-06 20:05 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=20190411070020.38749a8b@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=broonie@kernel$(echo .)org \
    --cc=lgirdwood@gmail$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=ranjani.sridharan@linux$(echo .)intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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