From: John Crispin <john@phrozen.org>
To: Alexandre Oliva <oliva@gnu.org>,
Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: Ralf Baechle <ralf@linux-mips.org>, linux-mips@linux-mips.org
Subject: Re: [3.13-rc regression] Unbreak Loongson2 and r4k-generic flush icache range
Date: Tue, 14 Jan 2014 11:37:18 +0100 [thread overview]
Message-ID: <52D5135E.9020407@phrozen.org> (raw)
In-Reply-To: <oriotmopal.fsf@livre.home>
i think all questions were already answered
http://www.linux-mips.org/archives/linux-mips/2014-01/msg00127.html
On 14/01/2014 11:01, Alexandre Oliva wrote:
> On Jan 13, 2014, Sergei Shtylyov <sergei.shtylyov@cogentembedded.com> wrote:
>
>> Hello.
>>> Commit 14bd8c08, that replaced Loongson2-specific ifdefs with cpu tests,
>>> inverted the CPU test in local_r4k_flush_icache_range. Loongson2 won't
>>> boot up using the generic icache flush code. Presumably other CPUs
>>> might face other problems when presented with Loongson2-specific icache
>>> flush code too. This patch enabled my Yeeloong to boot up successfully
>>> a 3.13-rc kernel for the first time, after a long git bisect session.
>>> Signed-off-by: Alexandre Oliva <lxoliva@fsfla.org>
>> Fix for this issue has been posted long ago:
>> http://marc.info/?l=linux-mips&m=138575576803890
> Thanks. As long ago as that was, I still don't see it in Torvalds's
> master branch. Was a pull request including this patch ever send his
> way? Such a trivial fix for such a show-stopper shouldn't find any
> difficulties making 3.13, I think.
>
prev parent reply other threads:[~2014-01-14 10:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 11:26 [3.13-rc regression] Unbreak Loongson2 and r4k-generic flush icache range Alexandre Oliva
2014-01-13 13:31 ` Sergei Shtylyov
2014-01-13 13:41 ` John Crispin
2014-01-13 18:26 ` Aaro Koskinen
2014-01-14 10:01 ` Alexandre Oliva
2014-01-14 10:37 ` John Crispin [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=52D5135E.9020407@phrozen.org \
--to=john@phrozen.org \
--cc=linux-mips@linux-mips.org \
--cc=oliva@gnu.org \
--cc=ralf@linux-mips.org \
--cc=sergei.shtylyov@cogentembedded.com \
/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