From: Paul Bolle <pebolle@tiscali.nl>
To: Jonas Bonn <jonas@southpole.se>
Cc: Guenter Roeck <linux@roeck-us.net>, anees <rean12is@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] OpenRISC: Fix kernel build problem on OpenRISC
Date: Wed, 13 May 2015 16:28:30 +0200 [thread overview]
Message-ID: <1431527310.2650.13.camel@x220> (raw)
In-Reply-To: <55535496.6050506@southpole.se>
On Wed, 2015-05-13 at 15:41 +0200, Jonas Bonn wrote:
> openrisc.net is no more.... long story, not worth regurgitating.
I see. What would you suggest as substitutes for:
MAINTAINERS:W: http://openrisc.net
MAINTAINERS:L: linux@lists.openrisc.net (moderated for non-subscribers)
MAINTAINERS:T: git git://openrisc.net/~jonas/linux
arch/openrisc/README.openrisc: website http://openrisc.net
arch/openrisc/README.openrisc:1) The toolchain can be obtained from openrisc.net. Instructions for building
arch/openrisc/README.openrisc:http://openrisc.net/toolchain-build.html
arch/openrisc/README.openrisc: git clone git://openrisc.net/jonas/or1ksim-svn
arch/openrisc/kernel/setup.c: printk(KERN_INFO "OpenRISC Linux -- http://openrisc.net\n");
Thanks,
Paul Bolle
next prev parent reply other threads:[~2015-05-13 14:28 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 [this message]
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
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=1431527310.2650.13.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=jonas@southpole.se \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox