From: Kumar Gala <galak@kernel.crashing.org>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Please pull from 'powerpc-next' branch (for 2.6.26)
Date: Tue, 13 May 2008 08:56:53 -0500 (CDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0805130854430.25874@blarg.am.freescale.net> (raw)
Please pull from 'powerpc-next' branch of
master.kernel.org:/pub/scm/linux/kernel/git/galak/powerpc.git powerpc-next
All of these changes are pretty much isolated to the board they touch so
the possibility of breaking things is minor. Also, the driver removal is
because we have superceded fec_8xx with fs_enet.
- k
to receive the following updates:
arch/powerpc/boot/dts/mpc8377_mds.dts | 27
arch/powerpc/boot/dts/mpc8610_hpcd.dts | 60 +
arch/powerpc/boot/dts/sbc8548.dts | 94 ++
arch/powerpc/configs/mpc8610_hpcd_defconfig | 95 +-
arch/powerpc/platforms/85xx/mpc85xx_mds.c | 121 ++
arch/powerpc/platforms/85xx/sbc8548.c | 30
arch/powerpc/platforms/86xx/mpc8610_hpcd.c | 15
drivers/net/Kconfig | 1
drivers/net/Makefile | 1
drivers/net/fec_8xx/Kconfig | 20
drivers/net/fec_8xx/Makefile | 12
drivers/net/fec_8xx/fec_8xx-netta.c | 151 ---
drivers/net/fec_8xx/fec_8xx.h | 220 ----
drivers/net/fec_8xx/fec_main.c | 1264 ----------------------------
drivers/net/fec_8xx/fec_mii.c | 418 ---------
15 files changed, 429 insertions(+), 2100 deletions(-)
Andy Fleming (2):
[POWERPC] 85xx: Add 8568 PHY workarounds to board code
[POWERPC] 85xx: Fix some sparse warnings for 85xx MDS
Anton Vorontsov (3):
[POWERPC] 86xx: mpc8610_hpcd: use ULI526X driver for on-board ethernet
[POWERPC] 86xx: mpc8610_hpcd: add support for NOR and NAND flashes
[POWERPC] 86xx: mpc8610_hpcd: fix second serial port
Becky Bruce (1):
[POWERPC] Delete unused fec_8xx net driver
Jeremy McNicoll (1):
[POWERPC] 85xx: SBC8548 - Add flash support and HW Rev reporting
Zhang Wei (1):
[POWERPC] 83xx: Enable DMA engine on the MPC8377 MDS board.
reply other threads:[~2008-05-13 14:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Pine.LNX.4.64.0805130854430.25874@blarg.am.freescale.net \
--to=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).