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>,
Quinn Tran <qutran@marvell.com>,
Himanshu Madhani <hmadhani@marvell.com>
Subject: linux-next: Fixes tag needs some work in the scsi-mkp tree
Date: Fri, 20 Dec 2019 16:19:08 +1100 [thread overview]
Message-ID: <20191220161908.10b18dcf@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 355 bytes --]
Hi all,
In commit
08c0de658b08 ("scsi: qla2xxx: Fix stuck login session using prli_pend_timer")
Fixes tag
Fixes: 974950710e2a ("qla2xxx: Fix stuck login session")
has these problem(s):
- Target SHA1 does not exist
Did you mean
Fixes: ce0ba496dccf ("scsi: qla2xxx: Fix stuck login session")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2019-12-20 5:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-20 5:19 Stephen Rothwell [this message]
2019-12-21 18:43 ` linux-next: Fixes tag needs some work in the scsi-mkp tree Martin K. Petersen
-- strict thread matches above, loose matches on Subject: below --
2021-11-04 4:37 Stephen Rothwell
2021-11-05 2:50 ` Martin K. Petersen
[not found] <CGME20210824063445epcas5p4ed6e40889cf8d78edd7914284b26e852@epcas5p4.samsung.com>
2021-08-24 6:34 ` Stephen Rothwell
2021-08-24 6:43 ` Alim Akhtar
2021-08-25 2:45 ` Martin K. Petersen
2020-08-18 6:11 Stephen Rothwell
2020-08-18 6:46 ` Can Guo
2019-11-19 9:28 Stephen Rothwell
2019-11-20 2:35 ` Martin K. Petersen
2019-08-29 23:40 Stephen Rothwell
2019-08-15 10:29 Stephen Rothwell
2019-08-20 1:53 ` Martin K. Petersen
2019-07-30 22:48 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=20191220161908.10b18dcf@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=hmadhani@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=qutran@marvell.com \
/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.