From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Date: Tue, 04 Jun 2019 07:27:06 +0000 Subject: Re: [PATCH 01/16] uaccess: add untagged_addr definition for other arches Message-Id: <20190604072706.GF15680@lst.de> List-Id: References: <20190601074959.14036-1-hch@lst.de> <20190601074959.14036-2-hch@lst.de> <431c7395-2327-2f7c-cc8f-b01412b74e10@oracle.com> In-Reply-To: <431c7395-2327-2f7c-cc8f-b01412b74e10@oracle.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Khalid Aziz Cc: Christoph Hellwig , Linus Torvalds , Paul Burton , James Hogan , Yoshinori Sato , Rich Felker , "David S. Miller" , Andrey Konovalov , Nicholas Piggin , Benjamin Herrenschmidt , Paul Mackerras , Michael Ellerman , linux-mips@vger.kernel.org, linux-sh@vger.kernel.org, sparclinux@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, linux-mm@kvack.org, x86@kernel.org, linux-kernel@vger.kernel.org, Catalin Marinas On Mon, Jun 03, 2019 at 09:16:08AM -0600, Khalid Aziz wrote: > Could you reword above sentence? We are already starting off with > untagged_addr() not being no-op for arm64 and sparc64. It will expand > further potentially. So something more along the lines of "Define it as > noop for architectures that do not support memory tagging". The first > paragraph in the log can also be rewritten to be not specific to arm64. Well, as of this patch this actually is a no-op for everyone. Linus, what do you think of applying this patch (maybe with a slightly fixed up commit log) to 5.2-rc so that we remove a cross dependency between the series?