From: Paul Martin <paul.martin@codethink.co.uk>
To: Aaro Koskinen <aaro.koskinen@nokia.com>
Cc: Guenter Roeck <linux@roeck-us.net>,
Rusty Russell <rusty@rustcorp.com.au>,
Aaro Koskinen <aaro.koskinen@iki.fi>,
linux-kernel@vger.kernel.org, Ralf Baechle <ralf@linux-mips.org>,
Florian Fainelli <f.fainelli@gmail.com>,
linux-mips@linux-mips.org
Subject: Re: mips build failures due to commit 8dd928915a73 (mips: fix up obsolete cpu function usage)
Date: Mon, 27 Apr 2015 14:44:28 +0100 [thread overview]
Message-ID: <20150427134427.GA5551@paulmartin.codethink.co.uk> (raw)
In-Reply-To: <20150427130343.GA26951@ak-desktop.emea.nsn-net.net>
On Mon, Apr 27, 2015 at 04:03:48PM +0300, Aaro Koskinen wrote:
> On Tue, Apr 21, 2015 at 08:41:08AM -0700, Guenter Roeck wrote:
> > The following might do it. Note that I can not really test it since I
> > don't have a real mips system, and qemu gets rcu hangs if I enable more
> > than one CPU (I see that with older kernels as well, so it is not a new
> > problem). Someone will have to test the patch on a real multi-core system.
>
> That works on Octeon+ EBH5600 board (8 cores) with 4.1-rc1.
>
> Tested-by: Aaro Koskinen <aaro.koskinen@nokia.com>
http://patchwork.linux-mips.org/patch/9828/
I've been using this patch since 21 Apr on the 4.1 merge HEAD on
EdgeRouter Pro (Octeon II, dual core). It's survived several
builds of gcc (using make -j3).
Tested-by: Paul Martin <paul.martin@codethink.co.uk>
--
Paul Martin http://www.codethink.co.uk/
Senior Software Developer, Codethink Ltd.
prev parent reply other threads:[~2015-04-27 13:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-20 19:40 mips build failures due to commit 8dd928915a73 (mips: fix up obsolete cpu function usage) Guenter Roeck
2015-04-20 20:06 ` 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-22 2:59 ` Florian Fainelli
2015-04-27 13:03 ` Aaro Koskinen
2015-04-27 13:44 ` Paul Martin [this message]
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=20150427134427.GA5551@paulmartin.codethink.co.uk \
--to=paul.martin@codethink.co.uk \
--cc=aaro.koskinen@iki.fi \
--cc=aaro.koskinen@nokia.com \
--cc=f.fainelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux@roeck-us.net \
--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 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).