Re: [PATCH v2 1/9] iomap: Constify ioreadX() iomem argument (as in generic implementation)

From
Geert Uytterhoeven <geert@linux-m68k.org>
Date
2020-01-09 12:00:54
Also in
dri-devel, linux-alpha, linux-arch, nouveau
Reply to
Krzysztof Kozlowski, 2020-01-08
On Wed, Jan 8, 2020 at 9:05 PM Krzysztof Kozlowski [off-list ref] 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 <geert@linux-m68k.org>
Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds
Thread (18 messages) 18 messages, 7 authors, last reply 2020-01-26
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help