From: Logan Gunthorpe <logang@deltatee.com>
To: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
linux-ntb@googlegroups.com, linux-crypto@vger.kernel.org,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Arnd Bergmann" <arnd@arndb.de>,
"Andy Shevchenko" <andy.shevchenko@gmail.com>,
"Horia Geantă" <horia.geanta@nxp.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Philippe Ombredanne" <pombredanne@nexb.com>,
"Kate Stewart" <kstewart@linuxfoundation.org>
Subject: Re: [PATCH v12 1/9] iomap: Fix sparse endian check warnings
Date: Mon, 19 Mar 2018 14:38:04 -0600 [thread overview]
Message-ID: <9a55914e-142c-2a1b-2eef-66d7922a58b8@deltatee.com> (raw)
In-Reply-To: <20180317190311.tdmx2vlcjttsjs5j@ltop.local>
Hi Luc,
Thanks for the feedback. I'll try to address your points in a v13 shortly.
Logan
On 18/03/18 10:13 AM, Luc Van Oostenryck wrote:
> it looks correct but if you should explain why the warning
> is not a valid one. Once done, you can then explain what problem
> you have fixed instead of saying you suppressed a warning.
>
>> Also, it looks like the wrong conversion function was used in
>
> I would suggest to split the patch in two since it does two
> different things which should have their own explanation.
>
>> diff --git a/lib/iomap.c b/lib/iomap.c
>> index 541d926da95e..a05d9fa21794 100644
>> --- a/lib/iomap.c
>> +++ b/lib/iomap.c
>> @@ -106,8 +106,10 @@ EXPORT_SYMBOL(ioread32be);
>> #endif
>>
>> #ifndef mmio_write16be
>> -#define mmio_write16be(val,port) __raw_writew(be16_to_cpu(val),port)
>> -#define mmio_write32be(val,port) __raw_writel(be32_to_cpu(val),port)
>> +#define mmio_write16be(val, port) \
>> + __raw_writew((u16 __force)cpu_to_be16(val), port)
>> +#define mmio_write32be(val, port) \
>> + __raw_writel((u32 __force)cpu_to_be32(val), port)
>> #endif
>
> I think that in this sort of replacement, it's better to not split
> the lines (even if larger than 80, that's it).
>
> -- Luc Van Oostenryck
>
next prev parent reply other threads:[~2018-03-19 20:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-16 15:48 [PATCH v12 0/9] Add io{read|write}64 to io-64-atomic headers Logan Gunthorpe
2018-03-16 15:48 ` [PATCH v12 1/9] iomap: Fix sparse endian check warnings Logan Gunthorpe
2018-03-18 16:13 ` Luc Van Oostenryck
2018-03-19 20:38 ` Logan Gunthorpe [this message]
2018-03-16 15:48 ` [PATCH v12 2/9] parisc: iomap: introduce io{read|write}64 Logan Gunthorpe
2018-03-16 15:48 ` [PATCH v12 3/9] powerpc: io.h: move iomap.h include so that it can use readq/writeq defs Logan Gunthorpe
2018-03-16 15:48 ` [PATCH v12 4/9] powerpc: iomap.c: introduce io{read|write}64_{lo_hi|hi_lo} Logan Gunthorpe
2018-03-16 15:48 ` [PATCH v12 5/9] iomap: " Logan Gunthorpe
2018-03-16 15:48 ` [PATCH v12 6/9] io-64-nonatomic: add io{read|write}64[be]{_lo_hi|_hi_lo} macros Logan Gunthorpe
2018-03-16 15:48 ` [PATCH v12 7/9] ntb: ntb_hw_intel: use io-64-nonatomic instead of in-driver hacks Logan Gunthorpe
2018-03-16 15:48 ` [PATCH v12 8/9] crypto: caam: cleanup CONFIG_64BIT ifdefs when using io{read|write}64 Logan Gunthorpe
2018-03-16 15:48 ` [PATCH v12 9/9] ntb: ntb_hw_switchtec: Cleanup 64bit IO defines to use the common header Logan Gunthorpe
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=9a55914e-142c-2a1b-2eef-66d7922a58b8@deltatee.com \
--to=logang@deltatee.com \
--cc=andy.shevchenko@gmail.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=horia.geanta@nxp.com \
--cc=kstewart@linuxfoundation.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ntb@googlegroups.com \
--cc=luc.vanoostenryck@gmail.com \
--cc=pombredanne@nexb.com \
--cc=tglx@linutronix.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