On Mon, Aug 17, 2020 at 12:53:45PM +0200, Greg Kroah-Hartman wrote:
> You can always do this just fine, as one single patch. You do know
> about the co-developed-by: line, right?
Agreed. Please keep the main iommu driver in one patch and use
co-developed-by. This makes it easier for me to review
On Tue, Feb 26, 2019 at 08:07:17PM +0800, lantianyu1...@gmail.com wrote:
> Lan Tianyu (3):
> x86/Hyper-V: Set x2apic destination mode to physical when x2apic is
> available
> HYPERV/IOMMU: Add Hyper-V stub IOMMU driver
> MAINTAINERS: Add Hyper-V IOMMU driver into Hyper-V CORE AND
t;
> Signed-off-by: Geert Uytterhoeven <ge...@linux-m68k.org>
> Reviewed-by: Mark Brown <broo...@kernel.org>
> Acked-by: Robin Murphy <robin.mur...@arm.com>
> Acked-by: Joerg Roedel <jroe...@suse.de>
Applied, thanks.
_
Hi,
On Wed, Jun 04, 2014 at 06:03:36PM +0300, Eli Billauer wrote:
I believe that I need a managed dma_map_single() my own driver,
which doesn't fall in the case of a single use: The driver allocates
its buffers with __get_free_pages() (or the to-be managed version of
it). Then it cuts the
On Tue, Jun 03, 2014 at 03:24:20PM -0600, Shuah Khan wrote:
On 06/01/2014 01:01 AM, Eli Billauer wrote:
I see the value of this interface in unmap case, this type of wrapper
can release dma buffers, drivers neglected to release leaving dangling
buffers.
However, driver writers should give
