From: Joerg Roedel <joro@8bytes.org>
To: Baoquan He <bhe@redhat.com>
Cc: iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
dyoung@redhat.com, xlpang@redhat.com, Vincent.Wan@amd.com
Subject: Re: [PATCH 0/4] iommu/amd: Clean up patches
Date: Mon, 19 Sep 2016 16:20:58 +0200 [thread overview]
Message-ID: <20160919142058.GA7566@8bytes.org> (raw)
In-Reply-To: <1473929453-3533-1-git-send-email-bhe@redhat.com>
Hi Baoquan,
On Thu, Sep 15, 2016 at 04:50:49PM +0800, Baoquan He wrote:
> These were found out when I tried to fix the kdump failure on system
> with AMD iommu. Pack them into this patchset since they are not related
> to the kdump issue and each other.
>
> Baoquan He (4):
> iommu/amd: clean up the cmpxchg64 invocation
> iommu/amd: Use standard bitmap operation to set bitmap
> iommu/amd: Free domain id when free a domain of struct dma_ops_domain
> iommu/amd: No need to wait iommu completion if no dte irq entry change
I applied patches 1-3, but patch 4 had some conflicts. Can you please
rebase this patch to my x86/amd branch and resend?
Thanks,
Joerg
next prev parent reply other threads:[~2016-09-19 14:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-15 8:50 [PATCH 0/4] iommu/amd: Clean up patches Baoquan He
2016-09-15 8:50 ` [PATCH 1/4] iommu/amd: clean up the cmpxchg64 invocation Baoquan He
2016-09-15 8:50 ` [PATCH 2/4] iommu/amd: Use standard bitmap operation to set bitmap Baoquan He
2016-09-15 8:50 ` [PATCH 3/4] iommu/amd: Free domain id when free a domain of struct dma_ops_domain Baoquan He
2016-09-15 8:50 ` [PATCH 4/4] iommu/amd: No need to wait iommu completion if no dte irq entry change Baoquan He
2016-09-20 1:05 ` [PATCH RESEND " Baoquan He
2016-09-20 9:56 ` Joerg Roedel
2016-09-20 10:14 ` Baoquan He
2016-09-19 14:20 ` Joerg Roedel [this message]
2016-09-20 1:07 ` [PATCH 0/4] iommu/amd: Clean up patches Baoquan He
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=20160919142058.GA7566@8bytes.org \
--to=joro@8bytes.org \
--cc=Vincent.Wan@amd.com \
--cc=bhe@redhat.com \
--cc=dyoung@redhat.com \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xlpang@redhat.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