From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Alexander Duyck <alexander.h.duyck@intel.com>
Cc: linux-mm@kvack.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [swiotlb PATCH v3 0/3] Add support for DMA writable pages being writable by the network stack.
Date: Wed, 9 Nov 2016 16:23:41 -0500 [thread overview]
Message-ID: <20161109212341.GC12670@char.us.oracle.com> (raw)
In-Reply-To: <20161109151639.25151.24290.stgit@ahduyck-blue-test.jf.intel.com>
On Wed, Nov 09, 2016 at 10:19:57AM -0500, Alexander Duyck wrote:
> This patch series is a subset of the patches originally submitted with the
> above patch title. Specifically all of these patches relate to the
> swiotlb.
>
> I wasn't sure if I needed to resubmit this series or not. I see that v2 is
> currently sitting in the for-linus-4.9 branch of the swiotlb git repo. If
> no updates are required for the previous set then this patch set can be
> ignored since most of the changes are just cosmetic.
I already had tested v2 so if you have patches that you want to put on top
of that please do send them.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2016-11-09 21:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 15:19 Alexander Duyck
2016-11-09 15:20 ` [swiotlb PATCH v3 1/3] swiotlb: remove unused swiotlb_map_sg and swiotlb_unmap_sg functions Alexander Duyck
2016-11-09 15:20 ` [swiotlb PATCH v3 2/3] swiotlb-xen: Enforce return of DMA_ERROR_CODE in mapping function Alexander Duyck
2016-11-09 15:20 ` [swiotlb PATCH v3 3/3] swiotlb: Add support for DMA_ATTR_SKIP_CPU_SYNC Alexander Duyck
2016-11-09 21:23 ` Konrad Rzeszutek Wilk [this message]
2016-11-09 21:29 ` [swiotlb PATCH v3 0/3] Add support for DMA writable pages being writable by the network stack Alexander Duyck
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=20161109212341.GC12670@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=alexander.h.duyck@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=netdev@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