public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v1 0/6] Update gdsys board support
Date: Wed, 05 Nov 2014 11:43:44 +0100	[thread overview]
Message-ID: <5459FF60.2050806@denx.de> (raw)
In-Reply-To: <CANVMifKEktzv7cLT=SosrTOj+Yyiam7kWrKcfj2+xAEnpU4x4Q@mail.gmail.com>

Hi Dirk,

On 05.11.2014 10:45, Dirk Eibach wrote:
> will you look after this series? I ask because there is also some
> mpc83xx stuff involved.

Yes, I just looked again. Not sure how we should handle this patch 
series. I can ack the PPC4xx and CFI flash related patches and someone 
else can pull this series (Kim for mpc83xx. Or Kim ack's the 83xx patch 
and I'll pull all and push it forward.

Comments?

Thanks,
Stefan

  reply	other threads:[~2014-11-05 10:43 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-29 15:03 [U-Boot] [PATCH v1 0/6] Update gdsys board support dirk.eibach at gdsys.cc
2014-10-29 15:03 ` [U-Boot] [PATCH v1 1/6] board: dlvision: Reduce memory footprint dirk.eibach at gdsys.cc
2014-10-29 15:03 ` [U-Boot] [PATCH v1 2/6] mtd: Handle 29LV800BT dirk.eibach at gdsys.cc
2014-10-29 15:03 ` [U-Boot] [PATCH v1 3/6] common: Fix cmd_fpgad addressing dirk.eibach at gdsys.cc
2014-10-29 15:03 ` [U-Boot] [PATCH v1 4/6] board: dlvision-10g: Compile fix dirk.eibach at gdsys.cc
2014-10-29 15:03 ` [U-Boot] [PATCH v1 5/6] board: iocon: Fix fpga index in print_fpga_info() dirk.eibach at gdsys.cc
2014-10-29 15:03 ` [U-Boot] [PATCH v1 6/6] mpc83xx: Add gdsys hrcon board dirk.eibach at gdsys.cc
2014-11-07  0:18   ` Kim Phillips
2014-11-07 12:56     ` Dirk Eibach
2014-11-05  9:45 ` [U-Boot] [PATCH v1 0/6] Update gdsys board support Dirk Eibach
2014-11-05 10:43   ` Stefan Roese [this message]
2014-11-05 12:00     ` Dirk Eibach
2014-11-05 12:13       ` Stefan Roese
2014-11-06  6:29         ` Dirk Eibach
2014-11-06 18:25           ` York Sun
2014-11-07  0:21             ` Kim Phillips
2014-11-07 12:58     ` Dirk Eibach
2014-11-07 16:19       ` Kim Phillips

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=5459FF60.2050806@denx.de \
    --to=sr@denx.de \
    --cc=u-boot@lists.denx.de \
    /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