All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Joerg Roedel <joro@8bytes.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Lu Baolu <baolu.lu@linux.intel.com>
Subject: linux-next: Fixes tag needs some work in the iommu tree
Date: Wed, 20 May 2020 04:36:31 +1000	[thread overview]
Message-ID: <20200520043631.41a150d2@canb.auug.org.au> (raw)

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

Hi all,

In commit

  ef0865631ae3 ("iommu/vt-d: Fix pointer cast warnings on 32 bit")

Fixes tag

  Fixes: d64d47f4f5678 ("iommu/vt-d: Add nested translation helper function")

has these problem(s):

  - Target SHA1 does not exist

Fixes tag

  Fixes: a3bea1a35c083 ("iommu/vt-d: Add bind guest PASID support")

has these problem(s):

  - Target SHA1 does not exist

Maybe you meant

Fixes: b0d1f8741b81 ("iommu/vt-d: Add nested translation helper function")
Fixes: 56722a4398a3 ("iommu/vt-d: Add bind guest PASID support")

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2020-05-19 18:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-19 18:36 Stephen Rothwell [this message]
2020-05-25 11:55 ` linux-next: Fixes tag needs some work in the iommu tree Joerg Roedel
  -- strict thread matches above, loose matches on Subject: below --
2025-02-11 21:12 Stephen Rothwell
2025-02-14  8:13 ` Joerg Roedel
2022-04-29 13:01 Stephen Rothwell
2022-05-04  8:33 ` Joerg Roedel
2021-04-15 21:51 Stephen Rothwell
2021-04-16  7:57 ` Dafna Hirschfeld
2020-06-30 21:01 Stephen Rothwell
2020-03-10 22:36 Stephen Rothwell
2020-03-13 13:26 ` Joerg Roedel
2019-09-01 21:36 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=20200520043631.41a150d2@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=baolu.lu@linux.intel.com \
    --cc=joro@8bytes.org \
    --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.