From: Stephen Williams <steve@icarus•com>
To: linuxppc-embedded@ozlabs•org
Cc: Willy Tarreau <willy@w•ods.org>
Subject: Re: PPC 405GPr support in linux 2.4.32
Date: Mon, 01 May 2006 08:21:14 -0700 [thread overview]
Message-ID: <4456276A.9050405@icarus.com> (raw)
In-Reply-To: <20060430164013.GA4631@dmt>
Marcelo Tosatti wrote:
> Folks,
>
> The v2.4 patch acceptance policy has been shifting gradually from
> "accept new features" to "critical fixes only", and at this point in
> time the goal is to have a minimal amount of modifications as possible.
>
> There should be no need for major patch reworking with reference to new
> v2.4 releases.
>
> Willy Tarreau created a repository of useful v2.4 patches for this sort
> of situations. Stephen, Eugene, I think the 405GPr patches are good candidates.
>
> http://w.ods.org/linux/kernel/2.4/lkup/hardware.html
This (and things like it) needs to be *much* better advertised.
I had no idea it existed, or where I would look for such a thing.
It does no one any good if no one thinks to look for it;-)
If course the next major question is how does one submit patches
to this system?
--
Steve Williams "The woods are lovely, dark and deep.
steve at icarus.com But I have promises to keep,
http://www.icarus.com and lines to code before I sleep,
http://www.picturel.com And lines to code before I sleep."
next prev parent reply other threads:[~2006-05-01 15:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-26 23:19 PPC 405GPr support in linux 2.4.32 Stephen Williams
2006-04-26 23:35 ` Matt Porter
2006-04-26 23:57 ` Stephen Williams
2006-04-27 18:01 ` Eugene Surovegin
2006-04-27 18:07 ` Eugene Surovegin
2006-04-27 18:32 ` Stephen Williams
2006-04-27 19:04 ` Eugene Surovegin
2006-04-30 16:40 ` Marcelo Tosatti
2006-05-01 15:21 ` Stephen Williams [this message]
2006-04-27 18:45 ` Re-configuring busybox that comes with DENX's ELDK SELF Randy Smith
2006-04-26 23:48 ` PPC 405GPr support in linux 2.4.32 Tolunay Orkun
2006-04-27 16:48 ` Stephen Williams
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=4456276A.9050405@icarus.com \
--to=steve@icarus$(echo .)com \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
--cc=willy@w$(echo .)ods.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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