From: Sven Luther <sven.luther@wanadoo.fr>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
Dale Farnsworth <dale@farnsworth.org>,
linuxppc-embedded@ozlabs.org, Nicolas DET <det.nicolas@free.fr>
Subject: [PATCH] final mv643xx_eth pegasos patch set ...
Date: Tue, 8 Mar 2005 20:28:05 +0100 [thread overview]
Message-ID: <20050308192805.GA13884@pegasos> (raw)
In-Reply-To: <1110266832.13607.267.camel@gaston>
Hello,
Ok, thanks for your help, here is the final (hopefully) and cleaned up version
of my patches :
1) mv643xx-eth-pegasos.diff
This is the arch/ppc/platform diff, benh, could you look it over, and merge
it in ? It is not really usefull without the mv643xx_eth.c changes, but dale
is going to move those in together with his patches.
2) linux-2.5-mv643xx-enet-pegasos.diff
This is just two small hunks against dale's linux-2.5-mv643xx-enet tree,
which include the SA_INTERRUPT -> SA_IRQ and the Kconfig change. Dale said
he would merge them with his stuff, hopefully for 2.6.12.
3) mv643xx-eth.diff
This is the linux-2.5-mv643xx-enet diff against 2.6.11, together with the
linux-2.5-mv643xx-enet-pegasos.diff changes, for those who want to build
against 2.6.11.
So to build against the linux-2.5-mv643xx-enet tree, you need 1) and 2) and to
build against 2.6.11 you need 1) and 3).
I am currently running the patches included in these changes, and will include
them in the debian 2.6.11 kernels unless i hear otherwise.
Friendly,
Sven Luther
next prev parent reply other threads:[~2005-03-08 19:28 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-26 0:14 [PATCH][PPC32] mv64x60 updates Mark A. Greer
2005-02-24 8:25 ` Sven Luther
2005-02-24 15:28 ` Mark A. Greer
2005-02-24 16:04 ` Sven Luther
2005-02-24 17:08 ` Mark A. Greer
2005-02-24 17:05 ` Sven Luther
2005-02-24 17:24 ` Dale Farnsworth
2005-03-05 19:27 ` Sven Luther
2005-03-05 20:32 ` Sven Luther
2005-03-05 22:51 ` Dale Farnsworth
2005-03-06 7:02 ` Sven Luther
2005-03-06 10:29 ` Dale Farnsworth
2005-03-06 19:10 ` Sven Luther
2005-03-06 19:48 ` Nicolas DET
2005-03-07 1:00 ` [PATCH][PPC32] " Dale Farnsworth
2005-03-07 6:52 ` Sven Luther
2005-03-07 10:56 ` Nicolas DET
2005-03-07 10:58 ` Nicolas DET
2005-03-07 12:30 ` James Chapman
2005-03-07 12:46 ` Sven Luther
2005-03-07 12:57 ` Nicolas DET
2005-03-07 13:20 ` Sven Luther
2005-03-07 17:24 ` Mark A. Greer
2005-03-07 13:23 ` Linwoes
2005-03-07 22:54 ` mv643xx_eth SA_SHIRQ support patch Dale Farnsworth
2005-03-08 6:49 ` Sven Luther
2005-03-08 7:27 ` Benjamin Herrenschmidt
2005-03-08 12:20 ` Dale Farnsworth
2005-03-08 12:15 ` Sven Luther
2005-03-08 12:42 ` Sven Luther
[not found] ` <20050308164310.GA9891@pegasos>
2005-03-08 22:31 ` Benjamin Herrenschmidt
2005-03-09 7:17 ` Sven Luther
2005-03-09 7:39 ` Benjamin Herrenschmidt
2005-03-09 7:40 ` Sven Luther
2005-03-08 18:19 ` Mark A. Greer
2005-03-08 18:19 ` Sven Luther
2005-03-08 19:28 ` Sven Luther [this message]
2005-03-08 19:52 ` [PATCH] final mv643xx_eth pegasos patch set Sven Luther
2005-03-08 23:18 ` Nicolas DET
2005-03-09 2:03 ` mv64x60 updates Benjamin Herrenschmidt
2005-03-09 2:01 ` Benjamin Herrenschmidt
2005-03-09 15:59 ` Chris Friesen
2005-03-05 21:58 ` [PATCH][PPC32] " Dale Farnsworth
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=20050308192805.GA13884@pegasos \
--to=sven.luther@wanadoo.fr \
--cc=benh@kernel.crashing.org \
--cc=dale@farnsworth.org \
--cc=det.nicolas@free.fr \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc-embedded@ozlabs.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.