From: Stephen Rothwell <sfr@canb•auug.org.au>
To: "Martin K. Petersen" <martin.petersen@oracle•com>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Tomas Henzl <thenzl@redhat•com>
Subject: linux-next: Fixes tag needs some work in the scsi-fixes tree
Date: Thu, 3 Sep 2020 18:47:38 +1000 [thread overview]
Message-ID: <20200903184738.53f62617@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 817 bytes --]
Hi all,
In commit
b614d55b970d ("scsi: mpt3sas: Don't call disable_irq from IRQ poll handler")
Fixes tag
Fixes: 320e77acb3 scsi: mpt3sas: Irq poll to avoid CPU hard lockups
has these problem(s):
- SHA1 should be at least 12 digits long
In commit
d2af39141eea ("scsi: megaraid_sas: Don't call disable_irq from process IRQ poll")
Fixes tag
Fixes: a6ffd5bf681 scsi: megaraid_sas: Call disable_irq from process IRQ poll
has these problem(s):
- SHA1 should be at least 12 digits long
These can be fixed in 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").
Also, Fixes tags are usually generated using
git log -1 --format='Fixes: %h ("%s")' <SHA1>
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2020-09-03 8:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-03 8:47 Stephen Rothwell [this message]
2020-09-04 1:51 ` linux-next: Fixes tag needs some work in the scsi-fixes tree Martin K. Petersen
-- strict thread matches above, loose matches on Subject: below --
2020-06-24 7:07 Stephen Rothwell
2020-06-24 7:14 ` SeongJae Park
2020-06-24 7:23 ` Stephen Rothwell
2020-05-08 11:33 Stephen Rothwell
2020-05-11 23:54 ` Martin K. Petersen
2019-02-05 20:20 Stephen Rothwell
2019-02-06 3:55 ` Vaibhav Jain
2019-02-06 4:34 ` Stephen Rothwell
2019-02-06 13:03 ` Martin K. Petersen
2019-01-29 20:53 Stephen Rothwell
2019-01-23 5:34 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=20200903184738.53f62617@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=martin.petersen@oracle$(echo .)com \
--cc=thenzl@redhat$(echo .)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