From: Can Guo <cang@codeaurora.org>
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>
Subject: Re: linux-next: Fixes tag needs some work in the scsi-mkp tree
Date: Tue, 18 Aug 2020 14:46:01 +0800 [thread overview]
Message-ID: <1ac7e6465cb70a74866cd5f5595af29e@codeaurora.org> (raw)
In-Reply-To: <20200818161121.77559bee@canb.auug.org.au>
Hi Stephen,
On 2020-08-18 14:11, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> 35afe60929ab ("scsi: ufs: Properly release resources if a task is
> aborted successfully")
>
> Fixes tag
>
> Fixes: 5a0b0cb9bee7 ("ufs: Add support for clock gating")
>
> has these problem(s):
>
> - Subject does not match target commit subject
> Just use
> git log -1 --format='Fixes: %h ("%s")'
>
> Did you mean
>
> Fixes: 5a0b0cb9bee7 ("[SCSI] ufs: Add support for sending NOP OUT
> UPIU")
>
> or
>
> Fixes: 1ab27c9cf8b6 ("ufs: Add support for clock gating")
Thanks for pointing it out, it should be below one, something
might go wrong with my copy-paste.
Fixes: 1ab27c9cf8b6 ("ufs: Add support for clock gating")
Regards,
Can Guo.
next prev parent reply other threads:[~2020-08-18 6:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 6:11 linux-next: Fixes tag needs some work in the scsi-mkp tree Stephen Rothwell
2020-08-18 6:46 ` Can Guo [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
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=1ac7e6465cb70a74866cd5f5595af29e@codeaurora.org \
--to=cang@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=martin.petersen@oracle.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 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.