From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Martin Wilck <mwilck@suse.com>
Subject: Re: linux-next: Fixes tag needs some work in the scsi-mkp tree
Date: Mon, 19 Aug 2019 21:53:14 -0400 [thread overview]
Message-ID: <yq1mug4zjp1.fsf@oracle.com> (raw)
In-Reply-To: <20190815202934.1fb36c38@canb.auug.org.au> (Stephen Rothwell's message of "Thu, 15 Aug 2019 20:29:34 +1000")
Stephen,
> In commit
>
> cff1191553d9 ("scsi: qla2xxx: cleanup trace buffer initialization")
>
> Fixes tag
>
> Fixes: ad0a0b01f088 ("scsi: qla2xxx: Fix Firmware dump size for Extended
>
> has these problem(s):
>
> - Subject has leading but no trailing parentheses
> - Subject has leading but no trailing quotes
>
> Please don't split Fixes tags over more than one line.
>
> Fixes tag
>
> Fixes: (a28d9e4ef997 "scsi: qla2xxx: Add support for multiple fwdump
>
> has these problem(s):
>
> - No SHA1 recognised
Fixed these up. Thanks!
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2019-08-20 1:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-15 10:29 linux-next: Fixes tag needs some work in the scsi-mkp tree Stephen Rothwell
2019-08-20 1:53 ` Martin K. Petersen [this message]
-- 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-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-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=yq1mug4zjp1.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mwilck@suse.com \
--cc=sfr@canb.auug.org.au \
/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).