From: Lorenzo Pieralisi <lpieralisi@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "Lukas Bulwahn" <lukas.bulwahn@gmail.com>,
"Marek Vasut" <marek.vasut+renesas@gmail.com>,
"Yoshihiro Shimoda" <yoshihiro.shimoda.uh@renesas.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
linux-pci@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI: rcar: avoid defines prefixed with CONFIG
Date: Thu, 2 Feb 2023 16:40:54 +0100 [thread overview]
Message-ID: <Y9vZhv2+F4e/Asko@lpieralisi> (raw)
In-Reply-To: <Y8GHICwCNRsYCva8@lpieralisi>
On Fri, Jan 13, 2023 at 05:30:24PM +0100, Lorenzo Pieralisi wrote:
> On Fri, Jan 13, 2023 at 10:05:09AM +0100, Geert Uytterhoeven wrote:
> > Hi Lukas,
> >
> > On Fri, Jan 13, 2023 at 9:52 AM Lukas Bulwahn <lukas.bulwahn@gmail.com> wrote:
> > > Defines prefixed with "CONFIG" should be limited to proper Kconfig options,
> > > that are introduced in a Kconfig file.
> > >
> > > Here, a definition for a bitmask to configure the SEND_ENABLE mode is named
> > > CONFIG_SEND_ENABLE.
> > >
> > > Rename this local definition to CONFIGURE_SEND_ENABLE to avoid defines
> > > prefixed with "CONFIG".
> > >
> > > No functional change.
> > >
> > > Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> >
> > Thanks for your patch!
> >
> > > --- a/drivers/pci/controller/pcie-rcar.h
> > > +++ b/drivers/pci/controller/pcie-rcar.h
> > > @@ -11,7 +11,7 @@
> > >
> > > #define PCIECAR 0x000010
> > > #define PCIECCTLR 0x000018
> > > -#define CONFIG_SEND_ENABLE BIT(31)
> > > +#define CONFIGURE_SEND_ENABLE BIT(31)
> >
> > The R-Car Gen3 rev. 2.30 Hardware User's Manual calls the bit "CCIE".
> >
> > Hence if I would have written the driver, I would have used
> >
> > #define PCIECCTLR_CCIE BIT(31) /* Configuration Send Enable */
>
> Should I change it when I merge it ? That makes sense actually.
If I don't hear from anybody I will make the change above and merge it.
Thanks,
Lorenzo
>
> Thanks,
> Lorenzo
>
> > > #define TYPE0 (0 << 8)
> > > #define TYPE1 BIT(8)
> > > #define PCIECDR 0x000020
> >
> > 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:[~2023-02-02 15:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 8:45 [PATCH] PCI: rcar: avoid defines prefixed with CONFIG Lukas Bulwahn
2023-01-13 9:05 ` Geert Uytterhoeven
2023-01-13 9:06 ` Geert Uytterhoeven
2023-01-13 16:30 ` Lorenzo Pieralisi
2023-02-02 15:40 ` Lorenzo Pieralisi [this message]
2023-01-13 13:58 ` Bjorn Helgaas
2023-03-10 12:36 ` Lorenzo Pieralisi
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=Y9vZhv2+F4e/Asko@lpieralisi \
--to=lpieralisi@kernel.org \
--cc=bhelgaas@google.com \
--cc=geert@linux-m68k.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=marek.vasut+renesas@gmail.com \
--cc=robh@kernel.org \
--cc=yoshihiro.shimoda.uh@renesas.com \
/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