From: Krzysztof Halasa <khc@pm.waw.pl>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-arm-kernel@lists.infradead.org,
lkml <linux-kernel@vger.kernel.org>
Subject: [PULL REQ] IXP4xx (ARM) for 2.6.36
Date: Tue, 10 Aug 2010 23:28:02 +0200 [thread overview]
Message-ID: <m3bp9a40pp.fsf@intrepid.localdomain> (raw)
Linus,
This is the stuff which didn't make it to 2.6.35 for some reason.
IXP4xx fixes and additional platform support. It's based on 2.6.34-final
but merges cleanly and works correctly. Please pull, thanks.
The following changes since commit 9fe6206f400646a2322096b56c59891d530e8d51:
Linux 2.6.35 (2010-08-01 15:11:14 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/chris/linux-2.6.git ixp4xx
Krzysztof Hałasa (5):
IXP4xx: Prevent HSS transmitter lockup by disabling FRaMe signals.
IXP4xx: Fix ixp4xx_crypto little-endian operation.
IXP4xx: Make mdio_bus struct static in the Ethernet driver.
IXP4xx: Fix sparse warnings in I/O primitives.
IXP4xx: Fix LL debugging on little-endian CPU.
Marc Zyngier (2):
ixp4xx: base support for Arcom Vulcan
ixp4xx/vulcan: add PCI support
arch/arm/mach-ixp4xx/Kconfig | 8 +
arch/arm/mach-ixp4xx/Makefile | 2 +
arch/arm/mach-ixp4xx/include/mach/debug-macro.S | 2 +
arch/arm/mach-ixp4xx/include/mach/io.h | 6 +-
arch/arm/mach-ixp4xx/vulcan-pci.c | 73 +++++++
arch/arm/mach-ixp4xx/vulcan-setup.c | 246 +++++++++++++++++++++++
drivers/crypto/ixp4xx_crypto.c | 21 ++
drivers/net/arm/ixp4xx_eth.c | 2 +-
drivers/net/wan/ixp4xx_hss.c | 2 +-
9 files changed, 357 insertions(+), 5 deletions(-)
create mode 100644 arch/arm/mach-ixp4xx/vulcan-pci.c
create mode 100644 arch/arm/mach-ixp4xx/vulcan-setup.c
--
Krzysztof Halasa
reply other threads:[~2010-08-10 21:28 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=m3bp9a40pp.fsf@intrepid.localdomain \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox