From: Guenter Roeck <linux@roeck-us.net>
To: linux-kernel@vger.kernel.org
Cc: Rusty Russell <rusty@rustcorp.com.au>,
Ralf Baechle <ralf@linux-mips.org>,
Florian Fainelli <f.fainelli@gmail.com>,
linux-mips@linux-mips.org
Subject: mips build failures due to commit 8dd928915a73 (mips: fix up obsolete cpu function usage)
Date: Mon, 20 Apr 2015 12:40:28 -0700 [thread overview]
Message-ID: <20150420194028.GA10814@roeck-us.net> (raw)
Hi,
the upstream kernel fails to build mips:nlm_xlp_defconfig,
mips:nlm_xlp_defconfig, mips:cavium_octeon_defconfig, and possibly
other targets, with errors such as
arch/mips/kernel/smp.c:211:2: error:
passing argument 2 of 'cpumask_set_cpu' discards 'volatile' qualifier
from pointer target type
arch/mips/kernel/process.c:52:2: error:
passing argument 2 of 'cpumask_test_cpu' discards 'volatile' qualifier
from pointer target type
arch/mips/cavium-octeon/smp.c:242:2: error:
passing argument 2 of 'cpumask_clear_cpu' discards 'volatile' qualifier
from pointer target type
The problem was introduced with commit 8dd928915a73 (" mips: fix up obsolete cpu
function usage"). I would send a patch to fix it, but I am not sure if removing
'volatile' from the variable declaration(s) would be a good idea.
I don't recall seeing the problem in -next, but unless I am missing something,
the patch never made it into -next to start with.
Guenter
next reply other threads:[~2015-04-20 19:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-20 19:40 Guenter Roeck [this message]
2015-04-20 20:06 ` mips build failures due to commit 8dd928915a73 (mips: fix up obsolete cpu function usage) Ralf Baechle
2015-04-20 20:19 ` Guenter Roeck
2015-04-20 21:09 ` Aaro Koskinen
2015-04-21 4:11 ` Guenter Roeck
2015-04-21 4:15 ` Rusty Russell
2015-04-21 15:41 ` Guenter Roeck
2015-04-21 15:41 ` Guenter Roeck
2015-04-21 15:41 ` Guenter Roeck
2015-04-22 2:59 ` Florian Fainelli
2015-04-27 13:03 ` Aaro Koskinen
2015-04-27 13:44 ` Paul Martin
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=20150420194028.GA10814@roeck-us.net \
--to=linux@roeck-us.net \
--cc=f.fainelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=rusty@rustcorp.com.au \
/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.