From: Ryan Mallon <rmallon@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: Tue, 30 Oct 2012 11:46:12 +1100 [thread overview]
Message-ID: <508F2354.3090801@gmail.com> (raw)
In-Reply-To: <m3a9vkahci.fsf@intrepid.localdomain>
On 18/10/12 09:01, Krzysztof Halasa wrote:
> Hi,
>
<snip>
>
> Unfortunately, as I already explained to you in
> https://lkml.org/lkml/2012/9/29/37, my resources for IXP4xx are very
> limited (and this isn't a paid job) and I'm in no way able to do what
> you require. This, coupled with my inability to make the patches end up
> upstream any other way, will make me post relevant MAINTAINERS changes
> shortly.
>
> 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.
I maintain a tree for the ep93xx, which is another legacy arm soc. I
also do this as a hobbyist, not as a paid position. Pushing patches to
mainline via arm-soc has been very easy. Basically I branch from Linus's
tree (typically 3.x-rc1), apply patches to one of a bunch of branches
(-devel, -fixes, etc) and then send pull requests to the arm-soc
maintainers prior to the merge window. I also have a aggregate branch
which is tested in next.
It takes very little of my time to maintain this tree. I cannot see how
it could be any harder than sending to Linus directly. Also, the arm-soc
maintainers, Arnd and Olof, have been very helpful in getting me started
with my maintainer tree, and in learning the development flow.
I would also rather get flamed by the arm-soc guys than Linus when I
make a mistake :-).
~Ryan
WARNING: multiple messages have this Message-ID (diff)
From: rmallon@gmail.com (Ryan Mallon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PULL REQ] IXP4xx changes for Linux 3.7
Date: Tue, 30 Oct 2012 11:46:12 +1100 [thread overview]
Message-ID: <508F2354.3090801@gmail.com> (raw)
In-Reply-To: <m3a9vkahci.fsf@intrepid.localdomain>
On 18/10/12 09:01, Krzysztof Halasa wrote:
> Hi,
>
<snip>
>
> Unfortunately, as I already explained to you in
> https://lkml.org/lkml/2012/9/29/37, my resources for IXP4xx are very
> limited (and this isn't a paid job) and I'm in no way able to do what
> you require. This, coupled with my inability to make the patches end up
> upstream any other way, will make me post relevant MAINTAINERS changes
> shortly.
>
> 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.
I maintain a tree for the ep93xx, which is another legacy arm soc. I
also do this as a hobbyist, not as a paid position. Pushing patches to
mainline via arm-soc has been very easy. Basically I branch from Linus's
tree (typically 3.x-rc1), apply patches to one of a bunch of branches
(-devel, -fixes, etc) and then send pull requests to the arm-soc
maintainers prior to the merge window. I also have a aggregate branch
which is tested in next.
It takes very little of my time to maintain this tree. I cannot see how
it could be any harder than sending to Linus directly. Also, the arm-soc
maintainers, Arnd and Olof, have been very helpful in getting me started
with my maintainer tree, and in learning the development flow.
I would also rather get flamed by the arm-soc guys than Linus when I
make a mistake :-).
~Ryan
next prev parent reply other threads:[~2012-10-30 0:46 UTC|newest]
Thread overview: 18+ 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-13 21:22 ` Krzysztof Halasa
2012-10-14 20:02 ` Arnd Bergmann
2012-10-14 20:02 ` Arnd Bergmann
2012-10-17 22:01 ` Krzysztof Halasa
2012-10-17 22:01 ` Krzysztof Halasa
2012-10-19 16:25 ` Jason Cooper
2012-10-19 16:25 ` Jason Cooper
2012-10-29 8:29 ` Richard Cochran
2012-10-29 8:29 ` Richard Cochran
2012-10-30 22:27 ` Arnd Bergmann
2012-10-30 22:27 ` Arnd Bergmann
2012-10-31 13:24 ` Jason Cooper
2012-10-31 13:24 ` Jason Cooper
2012-10-29 9:55 ` Russell King - ARM Linux
2012-10-29 9:55 ` Russell King - ARM Linux
2012-10-30 0:46 ` Ryan Mallon [this message]
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=508F2354.3090801@gmail.com \
--to=rmallon@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 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.