linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Anatolij Gustschin <agust@denx.de>
To: Grant Likely <grant.likely@secretlab.ca>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: Please pull 'next' branch of 5xxx tree (updated)
Date: Thu, 29 Sep 2011 15:45:58 +0200	[thread overview]
Message-ID: <20110929154558.4a595ff1@wker> (raw)
In-Reply-To: <CACxGe6s1K+rUbH7XinhHXqXvNzZ_QXwYfZHe8t1kzYj223ampg@mail.gmail.com>

Hi Grant,

On Thu, 29 Sep 2011 07:49:07 -0500
Grant Likely <grant.likely@secretlab.ca> wrote:
...
> > 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.

Thanks for pointing this out. Actually Heiko is the author of
the original patch. I've updated the next branch accordingly, so
here is a new pull request:

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

Heiko Schocher (2):
      powerpc/5200: add support for charon board
      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

Anatolij

      reply	other threads:[~2011-09-29 13:46 UTC|newest]

Thread overview: 3+ 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
2011-09-29 13:45   ` Anatolij Gustschin [this message]

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=20110929154558.4a595ff1@wker \
    --to=agust@denx.de \
    --cc=benh@kernel.crashing.org \
    --cc=grant.likely@secretlab.ca \
    --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).