From: Richard Cochran <richardcochran@gmail.com>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: Arnd Bergmann <arnd@arndb.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-arm-kernel@lists.infradead.org,
lkml <linux-kernel@vger.kernel.org>,
arm@kernel.org
Subject: Re: [PULL REQ] IXP4xx changes for Linux 3.7
Date: Mon, 29 Oct 2012 09:29:40 +0100 [thread overview]
Message-ID: <20121029082940.GC2527@netboy.at.omicron.at> (raw)
In-Reply-To: <m3a9vkahci.fsf@intrepid.localdomain>
On Thu, Oct 18, 2012 at 12:01:17AM +0200, Krzysztof Halasa wrote:
>
> Don't get me wrong. If I had time for this it could be different.
> Unfortunately IXP4xx is a legacy arch, and for me it's simply a hobby at
> this point. Given the raised barriers to participate, probably aimed at
> paid maintainers, I have to quit doing this.
>
> BTW since Imre has probably even much less time, it would be a good time
> to find someone to maintain IXP4xx code. I will be publishing (from time
> to time) my tree (I'm using the hw myself), so even simple
> cherry-picking would probably make some sense.
So if no one else wants to do this, then I am willing to look after
the IXP code. I think that I do have the time for it.
Thanks,
Richard
next prev parent reply other threads:[~2012-10-29 8:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-13 21:22 [PULL REQ] IXP4xx changes for Linux 3.7 Krzysztof Halasa
2012-10-14 20:02 ` Arnd Bergmann
2012-10-17 22:01 ` Krzysztof Halasa
2012-10-19 16:25 ` Jason Cooper
2012-10-29 8:29 ` Richard Cochran [this message]
2012-10-30 22:27 ` Arnd Bergmann
2012-10-31 13:24 ` Jason Cooper
2012-10-29 9:55 ` Russell King - ARM Linux
2012-10-30 0:46 ` Ryan Mallon
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=20121029082940.GC2527@netboy.at.omicron.at \
--to=richardcochran@gmail.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=khc@pm.waw.pl \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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