From: "Lendacky, Thomas" <Thomas.Lendacky@amd.com>
To: Christoph Hellwig <hch@lst.de>
Cc: "iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
Alexander Duyck <alexander.duyck@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Greg KH <gregkh@linuxfoundation.org>,
Robin Murphy <robin.murphy@arm.com>,
Guenter Roeck <linux@roeck-us.net>
Subject: Re: [PATCH] kernel/dma/direct: Do not include SME mask in the DMA supported check
Date: Mon, 17 Dec 2018 14:49:00 +0000 [thread overview]
Message-ID: <1423e1f4-425f-433e-6b85-0240b2f03aa2@amd.com> (raw)
In-Reply-To: <6954879c-90df-b6bd-7925-f0985980ed18@amd.com>
On 12/16/2018 05:41 PM, Tom Lendacky wrote:
> On 12/15/2018 04:55 AM, Christoph Hellwig wrote:
>> The mail seems to be so oddly encoded so that git-am fails on it. Can
>> you resend as plain text?
>
> Hmmm... not sure what happened with that, but yeah, looking at the message
> source shows something strange went on. Let me take a look and I'll try to
> get a good version to you tommorow (Monday).
Must have been something with stgit... just resent using git format-patch
and git send-email and it looks ok. Let me know if it's still not right
when it gets to you.
Thanks,
Tom
>
> Thanks,
> Tom
>
>>
next prev parent reply other threads:[~2018-12-17 14:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-13 22:51 [PATCH] kernel/dma/direct: Do not include SME mask in the DMA supported check Lendacky, Thomas
2018-12-15 10:55 ` Christoph Hellwig
[not found] ` <20181215105510.GA1806-jcswGhMUV9g@public.gmane.org>
2018-12-16 23:41 ` Lendacky, Thomas
2018-12-17 14:49 ` Lendacky, Thomas [this message]
2018-12-17 14:39 ` [RESEND PATCH] " Lendacky, Thomas
2018-12-17 17:02 ` Christoph Hellwig
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=1423e1f4-425f-433e-6b85-0240b2f03aa2@amd.com \
--to=thomas.lendacky@amd.com \
--cc=alexander.duyck@gmail.com \
--cc=benh@kernel.crashing.org \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=robin.murphy@arm.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