[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMuHMdUGkba3hiRJPEw26oBdc6_MK_eBO==Z9QeinaoeZv8Qbw@mail.gmail.com>
Date: Tue, 12 Apr 2022 11:45:22 +0200
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: Wolfram Sang <wsa+renesas@...g-engineering.com>
Cc: Krzysztof Kozlowski <krzk@...nel.org>,
Sergey Shtylyov <s.shtylyov@....ru>,
Duc Nguyen <duc.nguyen.ub@...esas.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@...renesas.com>,
Andrew Gabbasov <andrew_gabbasov@...tor.com>,
Linux-Renesas <linux-renesas-soc@...r.kernel.org>,
MTD Maling List <linux-mtd@...ts.infradead.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] memory: renesas-rpc-if: Simplify single/double data
register access
Hi Wolfram,
On Tue, Apr 12, 2022 at 11:42 AM Wolfram Sang
<wsa+renesas@...g-engineering.com> wrote:
> On Mon, Apr 11, 2022 at 02:55:29PM +0200, Geert Uytterhoeven wrote:
> > For manual write and read, factor out the common access to the first
> > data register by keeping track of the current data pointer.
> >
> > Signed-off-by: Geert Uytterhoeven <geert+renesas@...der.be>
>
> Works fine with reading/writing on a V3U, so:
>
> Tested-by: Wolfram Sang <wsa+renesas@...g-engineering.com>
>
> I agree the code is more concise. I am not sure, though, if it is really
> more readable. But I don't mind very much, so except for a small nit:
>
> Reviewed-by: Wolfram Sang <wsa+renesas@...g-engineering.com>
Thanks!
> > + if (nbytes == 8)
> > + regmap_write(rpc->regmap, RPCIF_SMWDR1, *p++);
> > + regmap_write(rpc->regmap, RPCIF_SMWDR0, *p++);
>
> Last '++' can be omitted?
I know. But I think it looks nicer this way ;-)
The compiler doesn't care anyway.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-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
Powered by blists - more mailing lists