From: Florian Fainelli <f.fainelli@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>, Jens Axboe <axboe@kernel.dk>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jaedon Shin <jaedon.shin@gmail.com>
Subject: Re: linux-next: Fixes tags need some work in the block tree
Date: Fri, 27 Dec 2019 12:27:18 -0800 [thread overview]
Message-ID: <45665759-a76f-5631-51bd-488b04f6bf03@gmail.com> (raw)
In-Reply-To: <20191228065553.6ba5d28f@canb.auug.org.au>
On 12/27/2019 11:55 AM, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> 1a3d78cb6e20 ("ata: ahci_brcm: BCM7425 AHCI requires AHCI_HFLAG_DELAY_ENGINE")
>
> Fixes tags
>
> Fixes: 9586114cf1e9 ("ata: ahci_brcmstb: add support MIPS-based platforms")
> Fixes: 423be77daabe ("ata: ahci_brcmstb: add quirk for broken ncq")
>
> have this problem:
>
> - Target SHA1s do not exist
>
> Perhaps you meant
>
> Fixes: 1980eb9bd7d7 ("ata: ahci_brcmstb: add support for MIPS-based platforms")
> Fixes: 7de3244530bf ("ata: ahci_brcmstb: disable NCQ for MIPS-based platforms")
Yes, those are the two that should have been used, the two commits were
extracted from a downstream tree where the upstream commits ended up
looking slightly different, my script does not (yet) rewrite those, Jens
would you want me to resubmit or can you rewrite the commit message in
place?
>
> or
>
> Fixes: b46f79bc78e0 ("ata: ahci_brcmstb: add a quirk for MIPS-based platforms")
>
--
Florian
next prev parent reply other threads:[~2019-12-27 20:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-27 19:55 linux-next: Fixes tags need some work in the block tree Stephen Rothwell
2019-12-27 20:27 ` Florian Fainelli [this message]
2019-12-27 20:29 ` Jens Axboe
2019-12-27 20:39 ` Stephen Rothwell
2019-12-27 20:44 ` Jens Axboe
2019-12-27 21:51 ` Florian Fainelli
-- strict thread matches above, loose matches on Subject: below --
2019-05-06 20:43 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=45665759-a76f-5631-51bd-488b04f6bf03@gmail.com \
--to=f.fainelli@gmail.com \
--cc=axboe@kernel.dk \
--cc=jaedon.shin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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