Re: [PATCH RFC 0/5] ARM: Raspberry Pi 4 DMA support

[PATCH RFC 0/5] ARM: Raspberry Pi 4 DMA support · Nicolas Saenz Julienne <hidden> · 2019-10-14
[PATCH RFC 1/5] dma/direct: turn ARCH_ZONE_DMA_BITS into a variable · Nicolas Saenz Julienne <hidden> · 2019-10-14
Re: [PATCH RFC 1/5] dma/direct: turn ARCH_ZONE_DMA_BITS into a variable · Christoph Hellwig <hch@infradead.org> · 2019-10-30
Re: [PATCH RFC 1/5] dma/direct: turn ARCH_ZONE_DMA_BITS into a variable · Nicolas Saenz Julienne <hidden> · 2019-10-31
Re: [PATCH RFC 1/5] dma/direct: turn ARCH_ZONE_DMA_BITS into a variable · Christoph Hellwig <hch@infradead.org> · 2019-10-31
Re: [PATCH RFC 1/5] dma/direct: turn ARCH_ZONE_DMA_BITS into a variable · Nicolas Saenz Julienne <hidden> · 2019-10-31
Re: [PATCH RFC 0/5] ARM: Raspberry Pi 4 DMA support · Catalin Marinas <catalin.marinas@arm.com> · 2019-10-14
Re: [PATCH RFC 0/5] ARM: Raspberry Pi 4 DMA support · Nicolas Saenz Julienne <hidden> · 2019-10-15
Re: [PATCH RFC 0/5] ARM: Raspberry Pi 4 DMA support · Catalin Marinas <catalin.marinas@arm.com> · 2019-10-15

From: Catalin Marinas <catalin.marinas@arm.com>
Date: 2019-10-15 17:46:22
Also in: linux-arm-kernel, linux-iommu, linux-s390, lkml

On Tue, Oct 15, 2019 at 09:48:22AM +0200, Nicolas Saenz Julienne wrote:

A little off topic but I was wondering if you have a preferred way to refer to
the arm architecture in a way that it unambiguously excludes arm64 (for example
arm32 would work).

arm32 should be fine. Neither arm64 nor arm32 are officially endorsed
ARM Ltd names (officially the exception model is AArch32 while the
instruction set is one of A32/T32/T16).

-- 
Catalin

`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