From: Russell King - ARM Linux <linux@arm•linux.org.uk>
To: Christian Borntraeger <borntraeger@de•ibm.com>
Cc: linux-kernel@vger•kernel.org,
linux-arm-kernel@lists•infradead.org, linux-next@vger•kernel.org
Subject: Re: [PATCH] arm/rpc: avoid static keyword removal via define
Date: Tue, 16 Dec 2014 11:40:56 +0000 [thread overview]
Message-ID: <20141216114056.GP11285@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <5490146A.3000408@de.ibm.com>
On Tue, Dec 16, 2014 at 12:15:54PM +0100, Christian Borntraeger wrote:
> Am 15.12.2014 um 09:48 schrieb Christian Borntraeger:
> > commit 4486b86368d7 ("[ARM] riscpc: fix decompressor font file handling")
> > introduced Makefile magic to avoid building a file two times. Using
> > -Dstatic= does break some assumptions on compiler.h that were introduced
> > for READ_ONCE.
> >
> > Lets just use sed on the copy instead of using a define.
> >
> > Signed-off-by: Christian Borntraeger <borntraeger@de•ibm.com>
> > Cc: Russell King <linux@arm•linux.org.uk>
>
> This fixed the linux-next build http://kisskb.ellerman.id.au/kisskb/target/1508/
> Unless anybody complains, I will send the pull request for the access_once tree tomorrow and I have this patch applied on top.
Please give me some time to look at this.
--
FTTC broadband for 0.8mile line: currently at 9.5Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2014-12-16 11:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-15 8:48 [PATCH 0/1] arm: Fix fallout from the access_once tree Christian Borntraeger
2014-12-15 8:48 ` [PATCH] arm/rpc: avoid static keyword removal via define Christian Borntraeger
2014-12-16 11:15 ` Christian Borntraeger
2014-12-16 11:40 ` Russell King - ARM Linux [this message]
2014-12-17 14:20 ` Christian Borntraeger
2014-12-17 15:29 ` Christian Borntraeger
2014-12-17 16:54 ` Russell King - ARM Linux
2014-12-17 19:45 ` Christian Borntraeger
2014-12-18 9:34 ` Christian Borntraeger
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=20141216114056.GP11285@n2100.arm.linux.org.uk \
--to=linux@arm$(echo .)linux.org.uk \
--cc=borntraeger@de$(echo .)ibm.com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.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