From: Christoph Hellwig <hch@infradead.org>
To: Liam Mark <lmark@codeaurora.org>
Cc: "Isaac J. Manjarres" <isaacm@codeaurora.org>,
Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
kernel-team@android.com, Pratik Patel <pratikp@codeaurora.org>
Subject: Re: [RFC PATCH] iommu/iova: Support limiting IOVA alignment
Date: Wed, 19 Feb 2020 18:38:23 -0800 [thread overview]
Message-ID: <20200220023823.GA11561@infradead.org> (raw)
In-Reply-To: <alpine.DEB.2.10.2002191517150.636@lmark-linux.qualcomm.com>
On Wed, Feb 19, 2020 at 03:22:36PM -0800, Liam Mark wrote:
> I am looking into how much of our allocation pattern details I can share.
Well if you can't share the details it is by defintion completely
irrelevant. Please don't waste our time.
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Liam Mark <lmark@codeaurora.org>
Cc: Will Deacon <will@kernel.org>,
"Isaac J. Manjarres" <isaacm@codeaurora.org>,
kernel-team@android.com, Robin Murphy <robin.murphy@arm.com>,
linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
Pratik Patel <pratikp@codeaurora.org>
Subject: Re: [RFC PATCH] iommu/iova: Support limiting IOVA alignment
Date: Wed, 19 Feb 2020 18:38:23 -0800 [thread overview]
Message-ID: <20200220023823.GA11561@infradead.org> (raw)
In-Reply-To: <alpine.DEB.2.10.2002191517150.636@lmark-linux.qualcomm.com>
On Wed, Feb 19, 2020 at 03:22:36PM -0800, Liam Mark wrote:
> I am looking into how much of our allocation pattern details I can share.
Well if you can't share the details it is by defintion completely
irrelevant. Please don't waste our time.
next prev parent reply other threads:[~2020-02-20 2:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 20:30 [RFC PATCH] iommu/iova: Support limiting IOVA alignment Liam Mark
2020-02-14 20:30 ` Liam Mark
2020-02-17 16:46 ` Robin Murphy
2020-02-17 16:46 ` Robin Murphy
2020-02-19 12:37 ` Will Deacon
2020-02-19 12:37 ` Will Deacon
2020-02-19 23:22 ` Liam Mark
2020-02-19 23:22 ` Liam Mark
2020-02-20 2:38 ` Christoph Hellwig [this message]
2020-02-20 2:38 ` Christoph Hellwig
2020-02-20 17:35 ` Robin Murphy
2020-02-20 17:35 ` Robin Murphy
2020-02-20 23:11 ` Liam Mark
2020-02-20 23:11 ` Liam Mark
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=20200220023823.GA11561@infradead.org \
--to=hch@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=isaacm@codeaurora.org \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lmark@codeaurora.org \
--cc=pratikp@codeaurora.org \
--cc=robin.murphy@arm.com \
--cc=will@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 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.