From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Christoph Hellwig <hch@infradead.org>,
Adrian Bunk <bunk@stusta.de>,
spyro@f2s.com, john@dnsworld.co.uk, linux-kernel@vger.kernel.org
Subject: Re: RFC: Remove the arm26 port
Date: Sun, 29 Jul 2007 13:31:20 +0100 [thread overview]
Message-ID: <20070729123119.GA25431@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20070729121012.GA1375@infradead.org>
On Sun, Jul 29, 2007 at 01:10:12PM +0100, Christoph Hellwig wrote:
> On Sun, Jul 29, 2007 at 01:50:40PM +0200, Adrian Bunk wrote:
> > Considering the state of the arm26 port, I do hereby suggest to remove
> > it from the Linx kernel since it's far from a usable state and doesn't
> > seem to come back into a usable state.
> >
> > If anyone wants to work on getting this port back into a usable state in
> > the forseeable future he should speak up now.
>
> Yes, please. This bitrotting code has been in the way for quite bit of
> cross-architecture work I've been doing.
>
> Btw, there's probably no point to Cc rmk as he's not involved with that
> stinkin' pile.
Definitely - I'd like to see it gone so hopefully I'll stop being copied
on every single janitorial change to it.
(And yes, I've re-enabled mail-followup-to since otherwise I can't
group-reply in mutt to everyone - without it I just get hch in the To:
header and an empty CC: with 'g'. Tough shit to those anti-mail-followup-to
people. It's the only thing that actually works.)
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
next prev parent reply other threads:[~2007-07-29 12:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-07 20:12 Status of the arm26 port? Adrian Bunk
2007-07-29 11:50 ` RFC: Remove the arm26 port Adrian Bunk
2007-07-29 12:10 ` Christoph Hellwig
2007-07-29 12:31 ` Russell King [this message]
2007-07-29 13:05 ` Dr. David Alan Gilbert
2007-07-29 22:58 ` ian
2007-07-30 11:49 ` [2.6 patch] " Adrian Bunk
2007-07-30 22:08 ` Satyam Sharma
2007-07-31 1:25 ` Andrew Morton
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=20070729123119.GA25431@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=bunk@stusta.de \
--cc=hch@infradead.org \
--cc=john@dnsworld.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=spyro@f2s.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