From: Stephen Rothwell <sfr@canb•auug.org.au>
To: "Martin K. Petersen" <martin.petersen@oracle•com>
Cc: Tyrel Datwyler <tyreld@linux•ibm.com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: Fixes tags need some work in the scsi-fixes tree
Date: Fri, 5 Mar 2021 08:12:33 +1100 [thread overview]
Message-ID: <20210305081233.6b8ad732@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1230 bytes --]
Hi all,
In commit
f4c5e949056d ("scsi: ibmvfc: Reinitialize sub-CRQs and perform channel enquiry after LPM")
Fixes tag
Fixes: 3034ebe26389 ("ibmvfc: add alloc/dealloc routines for SCSI Sub-CRQ Channels")
has these problem(s):
- Subject does not match target commit subject
In commit
5bc26ea9498a ("scsi: ibmvfc: Store return code of H_FREE_SUB_CRQ during cleanup")
Fixes tag
Fixes: 39e461fddff0 ("ibmvfc: map/request irq and register Sub-CRQ interrupt handler")
has these problem(s):
- Subject does not match target commit subject
In commit
98cf9a92b8d6 ("scsi: ibmvfc: Treat H_CLOSED as success during sub-CRQ registration")
Fixes tag
Fixes: 3034ebe26389 ("ibmvfc: add alloc/dealloc routines for SCSI Sub-CRQ Channels")
has these problem(s):
- Subject does not match target commit subject
In commit
2de4c19179b1 ("scsi: ibmvfc: Fix invalid sub-CRQ handles after hard reset")
Fixes tag
Fixes: 3034ebe26389 ("ibmvfc: add alloc/dealloc routines for SCSI Sub-CRQ Channels")
has these problem(s):
- Subject does not match target commit subject
Plese just use
git log -1 --format='Fixes: %h ("%s")'
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2021-03-04 21:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-04 21:12 Stephen Rothwell [this message]
2021-03-04 22:31 ` linux-next: Fixes tags need some work in the scsi-fixes tree Martin K. Petersen
2021-03-04 23:44 ` Tyrel Datwyler
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=20210305081233.6b8ad732@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=tyreld@linux$(echo .)ibm.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