public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Jonas Bonn <jonas@southpole.se>, anees <rean12is@gmail.com>,
	linux-kernel@vger.kernel.org,
	Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>
Subject: Re: [PATCH 1/1] OpenRISC: Fix kernel build problem on OpenRISC
Date: Thu, 11 Jun 2015 11:52:43 +0200	[thread overview]
Message-ID: <1434016363.2271.90.camel@x220> (raw)
In-Reply-To: <55789C4F.7000603@roeck-us.net>

On Wed, 2015-06-10 at 13:21 -0700, Guenter Roeck wrote:
> Wonder if I should step in as interim maintainer to handle urgent
> requests like this one. Comments, thoughts, anyone ?

This is about a pretty major build issue, that's been known for ten
months now, isn't? If that's correct, this is not an urgent request, but
a chronic issue. So in that case anyone who cares about OpenRISC should
consider taking over. Because this looks like an orphaned architecture
to me.

Am I being too strict?


Paul Bolle


  reply	other threads:[~2015-06-11  9:52 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 [this message]
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=1434016363.2271.90.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 \
    --cc=stefan.kristiansson@saunalahti.fi \
    /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