From: Oleksandr Natalenko <oleksandr@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
linux-mm@kvack.org, Arnaldo Carvalho de Melo <acme@redhat.com>,
Will Deacon <will@kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Song Liu <songliubraving@fb.com>,
Alexey Dobriyan <adobriyan@gmail.com>,
Marc Zyngier <maz@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kallsyms: work around bogus -Wrestrict warning
Date: Wed, 8 Jan 2020 10:23:04 +0100 [thread overview]
Message-ID: <20200108092304.6rgulye4zvgptxt7@butterfly.localdomain> (raw)
In-Reply-To: <20200107142512.b3d63df56ffee1ef471b6acd@linux-foundation.org>
Hi.
On Tue, Jan 07, 2020 at 02:25:12PM -0800, Andrew Morton wrote:
> gee, is that even worth "fixing"? Oleksandr, I've seen a couple of
> these false positives. Do we know if anyone is taking them to the gcc
> developers?
I'm not aware of such an effort. I tend to blame compiler as an option
of last resort, but if Arnd gathers enough examples (since he's working
on fixing/working around those), it would be reasonable to suggest him to
hand over those findings to gcc bugtracker.
--
Best regards,
Oleksandr Natalenko (post-factum)
Senior Software Maintenance Engineer
next prev parent reply other threads:[~2020-01-08 9:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-07 21:40 [PATCH] kallsyms: work around bogus -Wrestrict warning Arnd Bergmann
2020-01-07 22:25 ` Andrew Morton
2020-01-08 9:23 ` Oleksandr Natalenko [this message]
2020-01-08 1:26 ` Masami Hiramatsu
2020-01-09 22:02 ` Andrew Morton
2020-01-09 22:18 ` Arnd Bergmann
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=20200108092304.6rgulye4zvgptxt7@butterfly.localdomain \
--to=oleksandr@redhat.com \
--cc=acme@redhat.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=maz@kernel.org \
--cc=mhiramat@kernel.org \
--cc=songliubraving@fb.com \
--cc=tglx@linutronix.de \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).