From: Joerg Roedel <joro@8bytes.org>
To: Adam Zerella <adam.zerella@gmail.com>
Cc: iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iommu/amd: Fix sparse warnings
Date: Tue, 10 Sep 2019 10:17:16 +0200 [thread overview]
Message-ID: <20190910081716.GD3247@8bytes.org> (raw)
In-Reply-To: <20190907065812.19505-1-adam.zerella@gmail.com>
On Sat, Sep 07, 2019 at 04:58:12PM +1000, Adam Zerella wrote:
> drivers/iommu/amd_iommu.c | 4 ++--
> drivers/iommu/amd_iommu_init.c | 12 ++++++------
> 2 files changed, 8 insertions(+), 8 deletions(-)
Applied, thanks.
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2019-09-10 8:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-07 6:58 [PATCH] iommu/amd: Fix sparse warnings Adam Zerella
2019-09-10 8:17 ` Joerg Roedel [this message]
2019-09-10 9:11 ` 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=20190910081716.GD3247@8bytes.org \
--to=joro@8bytes.org \
--cc=adam.zerella@gmail.com \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@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 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).