From: Joerg Roedel <joro@8bytes.org>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: David Woodhouse <dwmw2@infradead.org>,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/7] iommu: Minor cleanups and dev_printk() usage
Date: Mon, 11 Feb 2019 12:09:40 +0100 [thread overview]
Message-ID: <20190211110940.GC32526@8bytes.org> (raw)
In-Reply-To: <154966319813.132359.14641436497228395449.stgit@bhelgaas-glaptop.roam.corp.google.com>
On Fri, Feb 08, 2019 at 04:05:33PM -0600, Bjorn Helgaas wrote:
> I've had these minor iommu cleanups lying around for a while, but the ugly
> dmesg logs from [1] prompted me to finally post them. Take what you like,
> ignore the rest, and tell me so I can clear out my queue of old stuff.
>
> These fix no actual bugs.
>
> [1] https://lore.kernel.org/linux-pci/1547649064-19019-1-git-send-email-liudongdong3@huawei.com
Applied patches 1-6 to their respective branches, thanks Bjorn.
prev parent reply other threads:[~2019-02-11 11:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-08 22:05 [PATCH v1 0/7] iommu: Minor cleanups and dev_printk() usage Bjorn Helgaas
2019-02-08 22:05 ` [PATCH v1 1/7] iommu: Use dev_printk() when possible Bjorn Helgaas
2019-02-08 22:05 ` [PATCH v1 2/7] iommu/amd: " Bjorn Helgaas
2019-02-08 22:06 ` [PATCH v1 3/7] iommu/vt-d: " Bjorn Helgaas
2019-02-08 22:06 ` [PATCH v1 4/7] iommu/vt-d: Remove unnecessary local variable initializations Bjorn Helgaas
2019-02-11 1:55 ` Lu Baolu
2019-02-11 3:33 ` Bjorn Helgaas
2019-02-11 3:38 ` Lu Baolu
2019-02-08 22:06 ` [PATCH v1 5/7] iommu/vt-d: Remove unused dmar_remove_one_dev_info() argument Bjorn Helgaas
2019-02-08 22:06 ` [PATCH v1 6/7] iommu/vt-d: Remove misleading "domain 0" test from domain_exit() Bjorn Helgaas
2019-02-08 22:06 ` [PATCH v1 7/7] iommu/vt-d: Simplify control flow Bjorn Helgaas
2019-02-11 11:09 ` Joerg Roedel [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=20190211110940.GC32526@8bytes.org \
--to=joro@8bytes.org \
--cc=dwmw2@infradead.org \
--cc=helgaas@kernel.org \
--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).