From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Tadeusz Struk <tadeusz.struk@linaro.org>,
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 scsi-mkp tree
Date: Thu, 4 Nov 2021 15:37:32 +1100 [thread overview]
Message-ID: <20211104153732.0cb0169a@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 425 bytes --]
Hi all,
In commit
559a5d048ec3 ("scsi: core: Remove command size deduction from scsi_setup_scsi_cmnd()")
Fixes tag
Fixes: 2ceda20f0a99a74a82b78870f3b3e5fa93087a7f
has these problem(s):
- missing subject
Pleas just use
git log -1 --format='Fixes: %h ("%s")' <commit>
so
Fixes: 2ceda20f0a99 ("scsi: core: Move command size detection out of the fast path")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2021-11-04 4:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-04 4:37 Stephen Rothwell [this message]
2021-11-05 2:50 ` linux-next: Fixes tag needs some work in the scsi-mkp tree 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
-- strict thread matches above, loose matches on Subject: below --
2020-08-18 6:11 Stephen Rothwell
2020-08-18 6:46 ` Can Guo
2019-12-20 5:19 Stephen Rothwell
2019-12-21 18:43 ` Martin K. Petersen
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=20211104153732.0cb0169a@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=tadeusz.struk@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).