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>,
Yong Wu <yong.wu@mediatek.com>,
Jacob Pan <jacob.jun.pan@linux.intel.com>
Subject: linux-next: Fixes tag needs some work in the iommu tree
Date: Mon, 2 Sep 2019 07:36:13 +1000 [thread overview]
Message-ID: <20190902073613.770d1885@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1010 bytes --]
Hi all,
In commit
7893b59b1e2d ("iommu/vt-d: Remove global page flush support")
Fixes tag
Fixes: 1c4f88b7f1f9 ("iommu/vt-d: Shared virtual address in scalable
has these problem(s):
- Subject has leading but no trailing parentheses
- Subject has leading but no trailing quotes
In commit
b9475b3471f8 ("iommu/mediatek: Fix VLD_PA_RNG register backup when suspend")
Fixes tag
Fixes: 30e2fccf9512 ("iommu/mediatek: Enlarge the validate PA range
has these problem(s):
- Subject has leading but no trailing parentheses
- Subject has leading but no trailing quotes
In commit
76ce65464fcd ("iommu/mediatek: Fix iova_to_phys PA start for 4GB mode")
Fixes tag
Fixes: 30e2fccf9512 ("iommu/mediatek: Enlarge the validate PA range
has these problem(s):
- Subject has leading but no trailing parentheses
- Subject has leading but no trailing quotes
Please do not split Fixes tags over more than one line.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2019-09-01 21:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-01 21:36 Stephen Rothwell [this message]
2020-03-10 22:36 linux-next: Fixes tag needs some work in the iommu tree Stephen Rothwell
2020-03-13 13:26 ` Joerg Roedel
2020-05-19 18:36 Stephen Rothwell
2020-05-25 11:55 ` Joerg Roedel
2020-06-30 21:01 Stephen Rothwell
2021-04-15 21:51 Stephen Rothwell
2021-04-16 7:57 ` Dafna Hirschfeld
2022-04-29 13:01 Stephen Rothwell
2022-05-04 8:33 ` Joerg Roedel
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=20190902073613.770d1885@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=jacob.jun.pan@linux.intel.com \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=yong.wu@mediatek.com \
/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;
as well as URLs for NNTP newsgroup(s).