From: SeongJae Park <sjpark@amazon•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>,
SeongJae Park <sjpark@amazon•de>
Subject: Re: linux-next: Fixes tag needs some work in the scsi-fixes tree
Date: Wed, 24 Jun 2020 09:14:47 +0200 [thread overview]
Message-ID: <20200624071447.19529-1-sjpark@amazon.com> (raw)
In-Reply-To: <20200624170742.4e9e9c96@canb.auug.org.au> (raw)
On Wed, 24 Jun 2020 17:07:42 +1000 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> [-- Attachment #1: Type: text/plain, Size: 385 bytes --]
>
> Hi all,
>
> In commit
>
> 46da547e21d6 ("scsi: lpfc: Avoid another null dereference in lpfc_sli4_hba_unset()")
>
> Fixes tag
>
> Fixes: 1ffdd2c0440d ("scsi: lpfc: resolve static checker warning inlpfc_sli4_hba_unset")
>
> has these problem(s):
>
> - Subject does not match target commit subject
> Just use
> git log -1 --format='Fixes: %h ("%s")'
Oops, sorry for the mistake. I will send the fixed version in reply to this.
Thanks,
SeongJae Park
>
> --
> Cheers,
> Stephen Rothwell
next prev parent reply other threads:[~2020-06-24 7:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-24 7:07 linux-next: Fixes tag needs some work in the scsi-fixes tree Stephen Rothwell
2020-06-24 7:14 ` SeongJae Park [this message]
2020-06-24 7:17 ` [PATCH v2] scsi: lpfc: Avoid another null dereference in lpfc_sli4_hba_unset() SeongJae Park
2020-06-24 7:23 ` linux-next: Fixes tag needs some work in the scsi-fixes tree Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2020-09-03 8:47 Stephen Rothwell
2020-09-04 1:51 ` Martin K. Petersen
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=20200624071447.19529-1-sjpark@amazon.com \
--to=sjpark@amazon$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=martin.petersen@oracle$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=sjpark@amazon$(echo .)de \
/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