From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Tony Breeds <tony@bakeyournoodle.com>
Cc: LinuxPPC-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH 7/8] 44x/476fpe: Add 476fpe SoC code
Date: Sat, 03 Dec 2011 07:58:17 +1100 [thread overview]
Message-ID: <1322859497.11728.13.camel@pasglop> (raw)
In-Reply-To: <1322725164-4391-8-git-send-email-tony@bakeyournoodle.com>
On Thu, 2011-12-01 at 18:39 +1100, Tony Breeds wrote:
> Based on original work by David 'Shaggy' Kliekamp.
Typo in Shaggy's last name :-)
Cheers,
Ben.
next prev parent reply other threads:[~2011-12-02 20:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-01 7:39 Add support for the currituck 476 platform from IBM (v2) Tony Breeds
2011-12-01 7:39 ` [PATCH 1/8] 44x/pci: Use PCI_BASE_ADDRESS_MEM_PREFETCH rather than magic value Tony Breeds
2011-12-01 7:39 ` [PATCH 2/8] 44x/pci: Add a want_sdr flag into ppc4xx_pciex_hwops Tony Breeds
2011-12-02 20:57 ` Benjamin Herrenschmidt
2011-12-01 7:39 ` [PATCH 3/8] 44x/pci: Setup the dma_window properties for each pci_controller Tony Breeds
2011-12-01 7:39 ` [PATCH 4/8] 44x: Removing dead CONFIG_PPC47x Tony Breeds
2011-12-01 7:39 ` [PATCH 5/8] powerpc/boot: Add extended precision shifts to the boot wrapper Tony Breeds
2011-12-01 7:39 ` [PATCH 6/8] powerpc/boot: Add mfdcrx Tony Breeds
2011-12-01 7:39 ` [PATCH 7/8] 44x/476fpe: Add 476fpe SoC code Tony Breeds
2011-12-02 20:58 ` Benjamin Herrenschmidt [this message]
2011-12-03 10:11 ` Tony Breeds
2011-12-03 13:33 ` Josh Boyer
2011-12-03 21:52 ` Tony Breeds
2011-12-01 7:39 ` [PATCH 8/8] 44x/currituck: Add support for the new IBM currituck platform Tony Breeds
2011-12-01 7:43 ` Add support for the currituck 476 platform from IBM (v2) Tony Breeds
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=1322859497.11728.13.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=tony@bakeyournoodle.com \
/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).