From: Grant Likely <grant.likely@secretlab.ca>
To: Anatolij Gustschin <agust@denx.de>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: Please pull 'next' branch of 5xxx tree
Date: Thu, 29 Sep 2011 07:49:07 -0500 [thread overview]
Message-ID: <CACxGe6s1K+rUbH7XinhHXqXvNzZ_QXwYfZHe8t1kzYj223ampg@mail.gmail.com> (raw)
In-Reply-To: <20110929113025.2b224cd3@wker>
[-- Attachment #1: Type: text/plain, Size: 1291 bytes --]
On Sep 29, 2011 4:31 AM, "Anatolij Gustschin" <agust@denx.de> wrote:
>
> Hi Ben,
>
> please pull another two mpc5xxx patches for next. These patches were
> queued in Grant's 'powerpc/next' branch a while ago, but a pull request
> have never been submitted for them. Thanks!
>
> Anatolij
>
> The following changes since commit
7680057cc4c7d9caada12767831bfd9738dd7b43:
>
> powerpc: Don't try OPAL takeover on old 970 blades (2011-09-29 17:04:59
+1000)
>
> are available in the git repository at:
> git://git.denx.de/linux-2.6-agust.git next
>
> Grant Likely (1):
> powerpc/5200: add support for charon board
Hmmm, I didn't actually write this patch. It looks like the author credit
got screwed up at some point.
g.
>
> Heiko Schocher (1):
> powerpc, tqm5200: update tqm5200_defconfig to fit for charon board.
>
> arch/powerpc/boot/dts/charon.dts | 236
++++++++++++++++++++++++++
> arch/powerpc/configs/52xx/tqm5200_defconfig | 20 ++-
> arch/powerpc/platforms/52xx/mpc5200_simple.c | 1 +
> 3 files changed, 249 insertions(+), 8 deletions(-)
> create mode 100644 arch/powerpc/boot/dts/charon.dts
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev
[-- Attachment #2: Type: text/html, Size: 1811 bytes --]
next prev parent reply other threads:[~2011-09-29 12:49 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 9:30 Please pull 'next' branch of 5xxx tree Anatolij Gustschin
2011-09-29 12:49 ` Grant Likely [this message]
2011-09-29 13:45 ` Please pull 'next' branch of 5xxx tree (updated) Anatolij Gustschin
-- strict thread matches above, loose matches on Subject: below --
2014-01-15 21:18 Please pull 'next' branch of 5xxx tree Anatolij Gustschin
2014-01-28 5:46 ` Anatolij Gustschin
2014-01-28 6:00 ` Benjamin Herrenschmidt
2014-01-28 6:22 ` Anatolij Gustschin
2014-01-29 7:46 ` Benjamin Herrenschmidt
2014-01-29 10:11 ` Gerhard Sittig
2014-01-29 20:50 ` Anatolij Gustschin
2013-11-04 0:11 Anatolij Gustschin
2013-09-03 20:39 Anatolij Gustschin
2013-09-05 6:50 ` Benjamin Herrenschmidt
2013-09-09 9:38 ` Anatolij Gustschin
2013-07-01 22:36 Anatolij Gustschin
2013-07-02 7:46 ` Benjamin Herrenschmidt
2013-07-02 8:00 ` Anatolij Gustschin
2013-07-02 8:29 ` Benjamin Herrenschmidt
2013-07-02 10:29 ` Benjamin Herrenschmidt
2013-07-02 10:35 ` Anatolij Gustschin
2013-04-29 9:42 Anatolij Gustschin
2013-02-19 23:57 Anatolij Gustschin
2012-12-11 8:23 Anatolij Gustschin
2012-09-24 14:45 Anatolij Gustschin
2012-03-20 17:04 Anatolij Gustschin
2012-03-20 22:30 ` Wolfram Sang
2012-03-20 23:32 ` Benjamin Herrenschmidt
2012-03-21 0:18 ` Anatolij Gustschin
2012-03-21 14:08 ` Stephen Rothwell
2012-03-21 0:56 ` Anatolij Gustschin
2011-09-30 6:31 Heiko Schocher
2011-09-30 6:38 ` Heiko Schocher
2011-09-22 23:20 Anatolij Gustschin
2011-09-23 0:15 ` Benjamin Herrenschmidt
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=CACxGe6s1K+rUbH7XinhHXqXvNzZ_QXwYfZHe8t1kzYj223ampg@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=agust@denx.de \
--cc=linuxppc-dev@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 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).