From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Marek Vasut <marek.vasut@gmail.com>
Cc: linux-pci <linux-pci@vger.kernel.org>,
Marek Vasut <marek.vasut+renesas@gmail.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Phil Edworthy <phil.edworthy@renesas.com>,
Simon Horman <horms+renesas@verge.net.au>,
Wolfram Sang <wsa@the-dreams.de>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH V3 3/6] PCI: rcar: Replace various variable types with unsigned ones for register values
Date: Mon, 25 Mar 2019 09:14:00 +0100 [thread overview]
Message-ID: <CAMuHMdWUv4-T4n_7Cft83-HEUEz4oSFmeAP5k50=41vemmxsAg@mail.gmail.com> (raw)
In-Reply-To: <20190323015359.7231-3-marek.vasut@gmail.com>
Hi Marek,
On Sat, Mar 23, 2019 at 2:54 AM <marek.vasut@gmail.com> wrote:
> From: Marek Vasut <marek.vasut+renesas@gmail.com>
>
> Replace various variable types with u32 or unsigned int type for
> variables holding register values, since the registers are 32bit.
> Note that rcar_pcie_msi_irq() still uses various variable types
> because both find_first_bit() and __fls() require various variable
> types as an argument.
>
> Signed-off-by: Marek Vasut <marek.vasut+renesas@gmail.com>
Thanks for your patch!
> --- a/drivers/pci/controller/pcie-rcar.c
> +++ b/drivers/pci/controller/pcie-rcar.c
> @@ -190,7 +190,8 @@ static int rcar_pcie_config_access(struct rcar_pcie *pcie,
> unsigned char access_type, struct pci_bus *bus,
> unsigned int devfn, int where, u32 *data)
> {
> - int dev, func, reg, index;
> + unsigned int dev, func, index;
> + u32 reg;
"reg" is not a register value, but an (unsigned) register offset, so IMHO
"unsigned int" is the right type.
With that fixed:
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
next prev parent reply other threads:[~2019-03-25 8:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-23 1:53 [PATCH V3 1/6] PCI: rcar: Clean up remaining macros defining bits marek.vasut
2019-03-23 1:53 ` [PATCH V3 2/6] PCI: rcar: Replace unsigned long with u32 in register accessors marek.vasut
2019-03-25 8:07 ` Geert Uytterhoeven
2019-03-25 11:24 ` Marek Vasut
2019-03-23 1:53 ` [PATCH V3 3/6] PCI: rcar: Replace various variable types with unsigned ones for register values marek.vasut
2019-03-25 8:14 ` Geert Uytterhoeven [this message]
2019-03-23 1:53 ` [PATCH V3 4/6] PCI: rcar: Replace (8 * n) with (n << 3) marek.vasut
2019-03-25 8:26 ` Geert Uytterhoeven
2019-03-25 11:34 ` Marek Vasut
2019-03-23 1:53 ` [PATCH V3 5/6] PCI: rcar: Clean up debug messages marek.vasut
2019-03-23 1:53 ` [PATCH V3 6/6] PCI: rcar: Fix 64bit MSI message address handling marek.vasut
2019-03-25 8:28 ` Geert Uytterhoeven
2019-03-25 8:03 ` [PATCH V3 1/6] PCI: rcar: Clean up remaining macros defining bits Geert Uytterhoeven
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAMuHMdWUv4-T4n_7Cft83-HEUEz4oSFmeAP5k50=41vemmxsAg@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=geert+renesas@glider.be \
--cc=horms+renesas@verge.net.au \
--cc=linux-pci@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=marek.vasut+renesas@gmail.com \
--cc=marek.vasut@gmail.com \
--cc=phil.edworthy@renesas.com \
--cc=wsa@the-dreams.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).