From: Will Deacon <will@kernel.org>
To: linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
Cc: catalin.marinas@arm.com, Jon.Grimm@amd.com,
kernel-team@android.com, Will Deacon <will@kernel.org>,
thomas.lendacky@amd.com
Subject: Re: [PATCH] iommu/amd: Add sanity check for interrupt remapping table length macros
Date: Fri, 11 Dec 2020 13:10:59 +0000 [thread overview]
Message-ID: <160769084268.2390072.5659488750209026923.b4-ty@kernel.org> (raw)
In-Reply-To: <20201210162436.126321-1-suravee.suthikulpanit@amd.com>
On Thu, 10 Dec 2020 10:24:36 -0600, Suravee Suthikulpanit wrote:
> Currently, macros related to the interrupt remapping table length are
> defined separately. This has resulted in an oversight in which one of
> the macros were missed when changing the length. To prevent this,
> redefine the macros to add built-in sanity check.
>
> Also, rename macros to use the name of the DTE[IntTabLen] field as
> specified in the AMD IOMMU specification. There is no functional change.
Applied to arm64 (for-next/iommu/core), thanks!
[1/1] iommu/amd: Add sanity check for interrupt remapping table length macros
https://git.kernel.org/arm64/c/5ae9a046a452
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
prev parent reply other threads:[~2020-12-11 13:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-10 16:24 [PATCH] iommu/amd: Add sanity check for interrupt remapping table length macros Suravee Suthikulpanit
2020-12-10 17:29 ` Jerry Snitselaar
2020-12-11 13:10 ` Will Deacon [this message]
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=160769084268.2390072.5659488750209026923.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=Jon.Grimm@amd.com \
--cc=catalin.marinas@arm.com \
--cc=iommu@lists.linux-foundation.org \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=suravee.suthikulpanit@amd.com \
--cc=thomas.lendacky@amd.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).