From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Alexander Lobakin <alobakin@pm.me>
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
Paul Burton <paulburton@kernel.org>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH mips-next 0/3] MIPS: fix the two most annoying sparse floods
Date: Thu, 25 Jun 2020 11:40:59 +0200 [thread overview]
Message-ID: <20200625094059.GA7660@alpha.franken.de> (raw)
In-Reply-To: <OXAnLrccR2GxIpepN5IUjppNnjyVAnjQmCIx2RmgpMLsOzOBgXMKYvmjivy4Rq0bAVf11R5V9_FwfGx-MML3dShuOOoPUtAHUHUedlVrW_g=@pm.me>
On Sat, Jun 20, 2020 at 09:33:38AM +0000, Alexander Lobakin wrote:
> This set addresses the two most annoying sparse floods when building the
> tree with C={1,2}: one in asm/io.h (in several mangle-port.h actually),
> and one in asm/checksum.h.
> Both of these comes from lack of forced typecasting and hence harmless,
> but complicates real bug hunting, as asm/io.h is included in almost
> every driver, while asm/checksum.h is included in lots of networking
> code.
>
> I also fixed two wrong __mem_ioswabq() macros while was nearby.
> Tested on Generic MIPS platform -- no more flooding in console (there's
> one more source in mips-cm.h, but it's included in just a few files, so
> not a real problem. It can be issued separately anyway), while objdump
> doesn't see any difference at all.
>
> Alexander Lobakin (3):
> MIPS: generic/ip32: io: fix __mem_ioswabq()
> MIPS: io: fix sparse flood on asm/io.h
> MIPS: checksum: fix sparse flooding on asm/checksum.h
>
> arch/mips/include/asm/checksum.h | 4 ++--
> .../include/asm/mach-cavium-octeon/mangle-port.h | 12 +++++++++---
> arch/mips/include/asm/mach-generic/mangle-port.h | 12 ++++++------
> arch/mips/include/asm/mach-ip27/mangle-port.h | 6 +++---
> arch/mips/include/asm/mach-ip30/mangle-port.h | 6 +++---
> arch/mips/include/asm/mach-ip32/mangle-port.h | 6 +++---
> arch/mips/include/asm/mach-tx39xx/mangle-port.h | 6 +++---
> arch/mips/include/asm/mach-tx49xx/mangle-port.h | 6 +++---
> 8 files changed, 32 insertions(+), 26 deletions(-)
series applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2020-06-25 9:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-20 9:33 [PATCH mips-next 0/3] MIPS: fix the two most annoying sparse floods Alexander Lobakin
2020-06-20 9:34 ` [PATCH mips-next 1/3] MIPS: generic/ip32: io: fix __mem_ioswabq() Alexander Lobakin
2020-06-20 9:34 ` [PATCH mips-next 2/3] MIPS: io: fix sparse flood on asm/io.h Alexander Lobakin
2020-06-20 9:35 ` [PATCH mips-next 3/3] MIPS: checksum: fix sparse flooding on asm/checksum.h Alexander Lobakin
2020-06-25 9:40 ` Thomas Bogendoerfer [this message]
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=20200625094059.GA7660@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=alexandre.belloni@bootlin.com \
--cc=alobakin@pm.me \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=paulburton@kernel.org \
/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