All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jens Axboe <axboe@kernel.dk>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Jaedon Shin <jaedon.shin@gmail.com>
Subject: linux-next: Fixes tags need some work in the block tree
Date: Sat, 28 Dec 2019 06:55:53 +1100	[thread overview]
Message-ID: <20191228065553.6ba5d28f@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 635 bytes --]

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")

or

Fixes: b46f79bc78e0 ("ata: ahci_brcmstb: add a quirk for MIPS-based platforms")

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2019-12-27 19:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-27 19:55 Stephen Rothwell [this message]
2019-12-27 20:27 ` linux-next: Fixes tags need some work in the block tree Florian Fainelli
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=20191228065553.6ba5d28f@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=axboe@kernel.dk \
    --cc=f.fainelli@gmail.com \
    --cc=jaedon.shin@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.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 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.