From mboxrd@z Thu Jan 1 00:00:00 1970 From: Krzysztof Kozlowski Subject: Re: [PATCH v3 1/4] iomap: Constify ioreadX() iomem argument (as in generic implementation) Date: Thu, 9 Jul 2020 09:32:49 +0200 Message-ID: <20200709073249.GA6335__46969.2128988513$1594279991$gmane$org@kozik-lap> References: <20200709072837.5869-1-krzk@kernel.org> <20200709072837.5869-2-krzk@kernel.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Return-path: Received: from mail-ed1-f65.google.com ([209.85.208.65]:39018 "EHLO mail-ed1-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726184AbgGIHc4 (ORCPT ); Thu, 9 Jul 2020 03:32:56 -0400 Content-Disposition: inline In-Reply-To: <20200709072837.5869-2-krzk@kernel.org> Sender: linux-arch-owner@vger.kernel.org List-ID: To: Richard Henderson , Ivan Kokshaysky , Matt Turner , "James E.J. Bottomley" , Helge Deller , Michael Ellerman , Benjamin Herrenschmidt , Paul Mackerras , Yoshinori Sato , Rich Felker , Kalle Valo , "David S. Miller" , Jakub Kicinski , Dave Jiang , Jon Mason , Allen Hubbe , "Michael S. Tsirkin" , Jason Wang , Arnd Bergmann , Geert Uytterhoeven On Thu, Jul 09, 2020 at 09:28:34AM +0200, Krzysztof Kozlowski wrote: > The ioreadX() and ioreadX_rep() helpers have inconsistent interface. On > some architectures void *__iomem address argument is a pointer to const, > on some not. > > Implementations of ioreadX() do not modify the memory under the address > so they can be converted to a "const" version for const-safety and > consistency among architectures. > > Suggested-by: Geert Uytterhoeven > Signed-off-by: Krzysztof Kozlowski > Reviewed-by: Geert Uytterhoeven > Reviewed-by: Arnd Bergmann I forgot to put here one more Ack, for PowerPC: Acked-by: Michael Ellerman (powerpc) https://lore.kernel.org/lkml/87ftedj0zz.fsf@mpe.ellerman.id.au/ Best regards, Krzysztof