[PATCH 0/3] Remove x86-specific code from generic headers · Thiago Jung Bauermann <hidden> · 2019-07-13
[PATCH 1/3] x86,s390: Move ARCH_HAS_MEM_ENCRYPT definition to arch/Kconfig · Thiago Jung Bauermann <hidden> · 2019-07-13
Re: [PATCH 1/3] x86,s390: Move ARCH_HAS_MEM_ENCRYPT definition to arch/Kconfig · Christoph Hellwig <hch@lst.de> · 2019-07-13
Re: [PATCH 1/3] x86, s390: Move ARCH_HAS_MEM_ENCRYPT definition to arch/Kconfig · janani <hidden> · 2019-07-15
Re: [PATCH 1/3] x86, s390: Move ARCH_HAS_MEM_ENCRYPT definition to arch/Kconfig · Thiago Jung Bauermann <hidden> · 2019-07-15
[PATCH 3/3] fs/core/vmcore: Move sev_active() reference to x86 arch code · Thiago Jung Bauermann <hidden> · 2019-07-13
[PATCH 2/3] DMA mapping: Move SME handling to x86-specific files · Thiago Jung Bauermann <hidden> · 2019-07-13
Re: [PATCH 2/3] DMA mapping: Move SME handling to x86-specific files · Christoph Hellwig <hch@lst.de> · 2019-07-13
Re: [PATCH 0/3] Remove x86-specific code from generic headers · Thiago Jung Bauermann <hidden> · 2019-07-13

Re: [PATCH 2/3] DMA mapping: Move SME handling to x86-specific files

From: Christoph Hellwig <hch@lst.de>
Date: 2019-07-13 07:29:13
Also in: linux-fsdevel, linux-iommu, linux-s390, lkml

While this looks generally good to me, I think we want to split this
into three patches:

 1) update the swiotlb printk
 2) removing the dma-mapping check and printk
 3) clean up the mem_encrypt.h interface.

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help