All of lore.kernel.org
 help / color / mirror / Atom feed
From: Holger Brunck <holger.brunck@keymile.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/6] arm/km: add support for portl2 board
Date: Wed, 08 Jun 2011 11:06:21 +0200	[thread overview]
Message-ID: <4DEF3B8D.5090105@keymile.com> (raw)
In-Reply-To: <F766E4F80769BD478052FB6533FA745D19FADEF238@SC-VEXCH4.marvell.com>

Hi Prafulla,

On 06/08/2011 10:35 AM, Prafulla Wadaskar wrote:
>> Subject: [PATCH 2/6] arm/km: add support for portl2 board
> 
> Can you add this board support after this patch series or last patch in this series?
> 

hm, 3/6 and 5/6 has dependencies to the portl2 support patch, but I think I can
handle this. So I will prepare an update serie 1/5 and a single patch for the
portl2 support ok? But only for my curiosity, what the reason for this need?

Best regards
Holger Brunck

  reply	other threads:[~2011-06-08  9:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-07 10:45 [U-Boot] [PATCH 0/6] updates for keymile ARM boards Holger Brunck
2011-06-07 10:45 ` [U-Boot] [PATCH 1/6] arm/km: remove unneeded define Holger Brunck
2011-06-07 10:45 ` [U-Boot] [PATCH 2/6] arm/km: add support for portl2 board Holger Brunck
2011-06-08  8:35   ` Prafulla Wadaskar
2011-06-08  9:06     ` Holger Brunck [this message]
2011-06-08  9:13       ` Prafulla Wadaskar
2011-06-08 10:36         ` Holger Brunck
2011-06-08 10:50           ` Prafulla Wadaskar
2011-06-07 10:45 ` [U-Boot] [PATCH 3/6] arm/km: ethernet support for Port-L2 and mgcoge3un Holger Brunck
2011-06-07 10:45 ` [U-Boot] [PATCH 4/6] arm/km: use board KM_ENV_BUS for CONFIG_I2C_ENV_EEPROM_BUS Holger Brunck
2011-06-07 10:45 ` [U-Boot] [PATCH 5/6] arm/km: enable PCIE_INIT for Port-L2 Holger Brunck
2011-06-07 10:45 ` [U-Boot] [PATCH 6/6] arm/km: replace suenx targets with km_kirkwood Holger Brunck

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=4DEF3B8D.5090105@keymile.com \
    --to=holger.brunck@keymile.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.