From: Joerg Roedel <joro@8bytes.org>
To: Gary R Hook <gary.hook@amd.com>
Cc: Randy Dunlap <rdunlap@infradead.org>,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 2/2] iommu/amd: Add basic debugfs infrastructure for AMD IOMMU
Date: Tue, 15 May 2018 15:46:03 +0200 [thread overview]
Message-ID: <20180515134603.GD18595@8bytes.org> (raw)
In-Reply-To: <5e45f38e-cb45-d4a1-f351-30543f787290@amd.com>
On Mon, May 14, 2018 at 03:00:50PM -0500, Gary R Hook wrote:
> This was brought up a few weeks ago in, I believe, version 3 of this patch.
> That question was discussed (because that's what I did the first time out),
> and _someone_ _else_ asked about why I didn't just do it the way I've done
> it here.
You don't have this problem if you put the code in amd_iommu.c in an
IOMMU_DEBUGFS ifdef.
Joerg
next prev parent reply other threads:[~2018-05-15 13:46 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 17:20 [PATCH v7 0/2] Base enablement of IOMMU debugfs support Gary R Hook
2018-05-14 17:20 ` Gary R Hook
[not found] ` <152631818082.18929.13970142119193316487.stgit-tq90VzyE+wXkLsZ8J5Uweg@public.gmane.org>
2018-05-14 17:20 ` [PATCH v7 1/2] iommu - Enable debugfs exposure of IOMMU driver internals Gary R Hook
2018-05-14 17:20 ` Gary R Hook
[not found] ` <152631842046.18929.1205439632866632871.stgit-tq90VzyE+wXkLsZ8J5Uweg@public.gmane.org>
2018-05-24 9:18 ` Greg KH
2018-05-24 9:18 ` Greg KH
[not found] ` <20180524091807.GA18148-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2018-06-05 16:48 ` Gary R Hook
2018-06-05 16:48 ` Gary R Hook
2018-05-14 17:20 ` [PATCH v7 2/2] iommu/amd: Add basic debugfs infrastructure for AMD IOMMU Gary R Hook
2018-05-14 17:20 ` Gary R Hook
2018-05-14 17:50 ` Randy Dunlap
[not found] ` <ba2bb6f7-77ea-4431-af0f-d20c19820d5d-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2018-05-14 20:00 ` Gary R Hook
2018-05-14 20:00 ` Gary R Hook
[not found] ` <5e45f38e-cb45-d4a1-f351-30543f787290-5C7GfCeVMHo@public.gmane.org>
2018-05-14 21:00 ` Randy Dunlap
2018-05-14 21:00 ` Randy Dunlap
2018-05-15 13:46 ` Joerg Roedel [this message]
[not found] ` <20180515134603.GD18595-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2018-05-18 15:20 ` Gary R Hook
2018-05-18 15:20 ` Gary R Hook
[not found] ` <4041cb33-19a2-5542-4211-1dce51de5e40-5C7GfCeVMHo@public.gmane.org>
2018-05-18 16:49 ` Randy Dunlap
2018-05-18 16:49 ` Randy Dunlap
2018-05-18 21:02 ` Gary R Hook
[not found] ` <3eefbef8-142e-0a29-3e97-536717f63a98-5C7GfCeVMHo@public.gmane.org>
2018-05-24 23:51 ` Gary R Hook
2018-05-24 23:51 ` Gary R Hook
2018-05-29 12:09 ` Joerg Roedel
2018-05-29 12:09 ` 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=20180515134603.GD18595@8bytes.org \
--to=joro@8bytes.org \
--cc=gary.hook@amd.com \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.