From: Guenter Roeck <linux@roeck-us.net>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: anees <rean12is@gmail.com>, Jonas Bonn <jonas@southpole.se>,
linux@lists.openrisc.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] OpenRISC: Fix kernel build problem on OpenRISC
Date: Wed, 13 May 2015 06:45:34 -0700 [thread overview]
Message-ID: <5553557E.1080505@roeck-us.net> (raw)
In-Reply-To: <1431524020.2650.7.camel@x220>
On 05/13/2015 06:33 AM, Paul Bolle wrote:
> On Wed, 2015-05-13 at 06:20 -0700, Guenter Roeck wrote:
>> Just remembered ... or just apply https://lkml.org/lkml/2014/9/19/11 instead.
>
> (That patch also suggests that "or12" in the patch we're discussing here
> is a typo.)
>
> This is problem is present now for none months, apparently. Your patch
The problem was already present when openrisc was introduced back in 2011;
see arch/openrisc/TODO.openrisc. I just tried to get it fixed to let me use
a more recent toolchain for my build tests.
> was supposed to be applied already (see
> https://lkml.org/lkml/2014/9/22/36 ), but clearly nothing happened.
> openrisc.net is for sale.
>
> What's going on here?
>
No idea :-(
Guenter
prev parent reply other threads:[~2015-05-13 13:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-12 13:45 [PATCH 1/1] OpenRISC: Fix kernel build problem on OpenRISC anees
2015-05-12 20:07 ` Guenter Roeck
2015-05-13 9:58 ` Paul Bolle
2015-05-13 13:20 ` Guenter Roeck
2015-05-13 13:33 ` Paul Bolle
2015-05-13 13:41 ` Jonas Bonn
2015-05-13 14:28 ` Paul Bolle
2015-05-13 14:44 ` Geert Uytterhoeven
2015-05-13 16:49 ` Guenter Roeck
2015-05-13 16:57 ` Guenter Roeck
2015-06-10 20:21 ` Guenter Roeck
2015-06-11 9:52 ` Paul Bolle
2015-06-11 15:42 ` Guenter Roeck
2015-05-13 13:45 ` Guenter Roeck [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=5553557E.1080505@roeck-us.net \
--to=linux@roeck-us.net \
--cc=jonas@southpole.se \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@lists.openrisc.net \
--cc=pebolle@tiscali.nl \
--cc=rean12is@gmail.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 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.