From: Marek Vasut <marek.vasut@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>, linux-pci@vger.kernel.org
Cc: 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-soc@vger.kernel.org
Subject: Re: [PATCH V2] PCI: rcar: Clean up the macros
Date: Sun, 8 Apr 2018 18:53:43 +0200 [thread overview]
Message-ID: <1043a359-7440-826b-5146-7dea494214b8@gmail.com> (raw)
In-Reply-To: <21dff119-07a4-e7b0-f3c0-b21721124232@infradead.org>
On 04/08/2018 06:51 PM, Randy Dunlap wrote:
> On 04/08/2018 09:34 AM, Marek Vasut wrote:
>> On 04/08/2018 05:27 PM, Randy Dunlap wrote:
>>> On 04/08/2018 06:09 AM, Marek Vasut wrote:
>>>> This patch replaces the (1 << n) with BIT(n) and cleans up whitespace,
>>>> no functional change.
>>>>
>>>> Signed-off-by: Marek Vasut <marek.vasut+renesas@gmail.com>
>>>> Cc: Geert Uytterhoeven <geert+renesas@glider.be>
>>>> Cc: Phil Edworthy <phil.edworthy@renesas.com>
>>>> Cc: Simon Horman <horms+renesas@verge.net.au>
>>>> Cc: Wolfram Sang <wsa@the-dreams.de>
>>>> Cc: linux-renesas-soc@vger.kernel.org
>>>> ---
>>>> V2: Reword the commit message
>>>> ---
>>>> drivers/pci/host/pcie-rcar.c | 52 ++++++++++++++++++++++----------------------
>>>> 1 file changed, 26 insertions(+), 26 deletions(-)
>>>>
>>>> diff --git a/drivers/pci/host/pcie-rcar.c b/drivers/pci/host/pcie-rcar.c
>>>> index 25f68305322c..5ab7bf6a8de0 100644
>>>> --- a/drivers/pci/host/pcie-rcar.c
>>>> +++ b/drivers/pci/host/pcie-rcar.c
>>>> @@ -30,9 +30,9 @@
>>>
>>> missing this:
>>>
>>> #include <linux/bitops.h>
>>
>> This compiles just fine without it though, which means it's probably
>> pulled in through some of the other includes already present.
>>
>
> I suspected that. However, please see rule #1 in
> Documentation/process/submit-checklist.rst:
>
> 1) If you use a facility then #include the file that defines/declares
> that facility. Don't depend on other header files pulling in ones
> that you use.
If I was to include every single header from which I use something,
wouldn't that make the list real long then ? Is that really worth it?
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2018-04-08 16:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-08 13:09 [PATCH V2] PCI: rcar: Clean up the macros Marek Vasut
2018-04-08 15:27 ` Randy Dunlap
2018-04-08 16:34 ` Marek Vasut
2018-04-08 16:51 ` Randy Dunlap
2018-04-08 16:53 ` Marek Vasut [this message]
2018-04-08 18:03 ` Randy Dunlap
2018-04-08 18:26 ` Marek Vasut
2018-04-08 17:26 ` Niklas Söderlund
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=1043a359-7440-826b-5146-7dea494214b8@gmail.com \
--to=marek.vasut@gmail.com \
--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=phil.edworthy@renesas.com \
--cc=rdunlap@infradead.org \
--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).