From: eric.engestrom@imgtec•com (Eric Engestrom)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 4/4] ARM: remove duplicate const qualifier
Date: Mon, 25 Apr 2016 15:37:31 +0100 [thread overview]
Message-ID: <20160425143731.GR32731@imgtec.com> (raw)
In-Reply-To: <alpine.LFD.2.20.1604250953200.5091@knanqh.ubzr>
On Mon, Apr 25, 2016 at 10:12:16AM -0400, Nicolas Pitre wrote:
> Beware.
>
> I added many of those exactly because gcc did not ignore them when
> compiling with LTO where the lack of a const qualifier to qualify the
> actual array content, and not only the reference to that content,
> generated build errors due to section mismatches from the __initconst
> annotation.
I believe the first `const` does that, without the need for a second.
> So this is a NAK from me unless you may confirm that LTO builds are
> unaffected by your changes.
I can't confirm it (haven't tried), and don't care enough to do it :]
I guess I'm just dropping the patch then. Like I said, it can't hurt to
leave them in.
Cheers,
Eric
next prev parent reply other threads:[~2016-04-25 14:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1461577678-29517-1-git-send-email-eric.engestrom@imgtec.com>
2016-04-25 9:47 ` [PATCH 2/4] drivers: firmware: psci: remove duplicate const qualifier Eric Engestrom
2016-04-25 10:33 ` Jisheng Zhang
2016-04-25 9:47 ` [PATCH 3/4] dmaengine: pxa_dma: " Eric Engestrom
2016-04-25 19:18 ` Robert Jarzmik
2016-04-26 16:30 ` Vinod Koul
2016-04-25 9:47 ` [PATCH 4/4] ARM: " Eric Engestrom
2016-04-25 9:52 ` Viresh Kumar
2016-04-25 9:57 ` Alexandre Belloni
2016-04-25 10:39 ` Eric Engestrom
2016-04-25 11:38 ` Arnd Bergmann
2016-04-25 12:58 ` Eric Engestrom
2016-04-25 14:12 ` Nicolas Pitre
2016-04-25 14:37 ` Eric Engestrom [this message]
2016-04-26 10:12 ` Krzysztof Hałasa
2016-04-27 20:01 ` Nicolas Pitre
2016-04-25 10:59 ` Sylvain Lemieux
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=20160425143731.GR32731@imgtec.com \
--to=eric.engestrom@imgtec$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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