From: Jason Cooper <jason@lakedaemon.net>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Richard Cochran <richardcochran@gmail.com>,
Imre Kaloz <kaloz@openwrt.org>, Krzysztof Halasa <khc@pm.waw.pl>,
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: Wed, 31 Oct 2012 09:24:05 -0400 [thread overview]
Message-ID: <20121031132405.GD22042@titan.lakedaemon.net> (raw)
In-Reply-To: <201210302227.55857.arnd@arndb.de>
On Tue, Oct 30, 2012 at 10:27:55PM +0000, Arnd Bergmann wrote:
> On Monday 29 October 2012, Richard Cochran wrote:
> > 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 for the offer!
Yes, thank you!
> Jason Cooper was also volunteering to help out with this, and even we can't
> convince Krzysztof to continue doing it, there is also Imre who is officially
> listed as maintainer for IXP4xx and who has not commented on this. As Krzysztof
> mentions, he probably doesn't have much time for it, but I'd like to give
> him the chance to comment as well.
Agreed.
> I'm sure we can find some solution between the four of you. Right now, I think
> we should focus on getting the bug fixes from Krzysztof's tree into mainline
> and the stable kernels where applicable, and then establish a better working
> mode for the future kernels.
We also need to keep an eye on the big picture. If we are going to
keep/maintain ixp4xx in the kernel, there are some things which need to
be done. The drivers need moved to drivers/, platform headers need
moved to platform_data/, and we may as well add devicetree bindings
while we're moving things around.
Making ixp4xx compatible with multiplatform zImage would probably help
out the embedded distros as well.
thx,
Jason.
next prev parent reply other threads:[~2012-10-31 13:24 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
2012-10-30 22:27 ` Arnd Bergmann
2012-10-31 13:24 ` Jason Cooper [this message]
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=20121031132405.GD22042@titan.lakedaemon.net \
--to=jason@lakedaemon.net \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=kaloz@openwrt.org \
--cc=khc@pm.waw.pl \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richardcochran@gmail.com \
--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