From: Guenter Roeck <linux@roeck-us.net>
To: Christoph Lameter <cl@linux.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Tejun Heo <tj@kernel.org>
Subject: Re: linux-next: Tree for Aug 29
Date: Mon, 01 Sep 2014 15:00:01 -0700 [thread overview]
Message-ID: <5404EC61.9060907@roeck-us.net> (raw)
In-Reply-To: <alpine.DEB.2.11.1409011615210.22966@gentwo.org>
On 09/01/2014 02:15 PM, Christoph Lameter wrote:
> On Mon, 1 Sep 2014, Guenter Roeck wrote:
>
>> arch/ia64/sn/kernel/setup.c: In function 'sn_cpu_init':
>> arch/ia64/sn/kernel/setup.c:632:13: error: lvalue required as left operand of assignment
>> make[1]: *** [arch/ia64/sn/kernel/setup.o] Error 1
>> make: *** [arch/ia64/sn/kernel/setup.o] Error 2
>
>
> Subject: ia64: sn_nodepda cannot be assigned to after this_cpu conversion. Use __this_cpu_write.
>
> There must be an explit statement to modify the percpu variable after the conversion of the
> sn_nodpda macro to use this_cpu_read.
>
> Signed-off-by: Christoph Lameter <cl@linux.com>
>
FWIW: Compile-tested-by: Guenter Roeck <linux@roeck-us.net>
Too bad there is no ia64 support in qemu; this could use some "real" testing.
Guenter
next prev parent reply other threads:[~2014-09-01 22:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-29 5:07 linux-next: Tree for Aug 29 Stephen Rothwell
2014-08-29 11:28 ` Mark Brown
2014-09-01 17:35 ` Guenter Roeck
2014-09-01 21:15 ` Christoph Lameter
2014-09-01 22:00 ` Guenter Roeck [this message]
2014-09-02 15:54 ` Tejun Heo
-- strict thread matches above, loose matches on Subject: below --
2025-08-29 4:47 Stephen Rothwell
2024-08-29 7:25 Stephen Rothwell
2023-08-29 6:53 Stephen Rothwell
2022-08-29 5:53 Stephen Rothwell
2019-08-29 11:08 Stephen Rothwell
2018-08-29 3:40 Stephen Rothwell
2017-08-29 9:16 Stephen Rothwell
2013-08-29 10:00 Stephen Rothwell
2013-08-29 10:00 ` Stephen Rothwell
2011-08-29 6:19 Stephen Rothwell
2011-08-29 6:52 ` Sedat Dilek
2011-08-29 7:19 ` Stephen Rothwell
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=5404EC61.9060907@roeck-us.net \
--to=linux@roeck-us.net \
--cc=cl@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tj@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.