public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Peter Tyser <ptyser@xes-inc.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 00/10] Add support for TI OMAP4 SDP and Panda
Date: Fri, 18 Jun 2010 16:10:48 -0500	[thread overview]
Message-ID: <1276895448.31352.81.camel@petert> (raw)
In-Reply-To: <1276893761-3526-1-git-send-email-steve@sakoman.com>

Hi Steve,

> Steve Sakoman (10):
>   ARM: Rename arch/arm/cpu/arm_cortexa8 to armv7
>   ARMV7: Add basic support for TI OMAP4
>   ARMV7: Add support for TI OMAP4430 SDP
>   ARMV7: Add support for TI OMAP4 Panda
>   ARMV7: Restructure OMAP mmc driver to allow code sharing between
>     OMAP3 and OMAP4
>   ARMV7: Enable mmc support on TI OMAP4430 SDP
>   ARMV7: Enable mmc support on TI OMAP4 Panda
>   ARMV7: Restructure OMAP i2c driver to allow code sharing between
>     OMAP3 and OMAP4
>   ARMV7: Enable i2c support on TI OMAP4 SDP
>   ARMV7: Enable i2c support on TI OMAP4 Panda

It'd be preferred if you could reorganize the patch series to first make
all CPU/SOC changes, then finally do 1 patch for each board.  This is
generally considered cleaner than having patches bouncing back and forth
between common and board specific code.  Right now the SDP and Panda
boards each require 3 patches when 1 patch apiece should suffice.  eg:
ARM: Rename arch/arm/cpu/arm_cortexa8 to armv7
ARMV7: Add basic support for TI OMAP4
ARMV7: Restructure OMAP mmc driver to allow code sharing between OMAP3 and OMAP4
ARMV7: Restructure OMAP i2c driver to allow code sharing between OMAP3 and OMAP4
ARMV7: Add support for TI OMAP4430 SDP
ARMV7: Add support for TI OMAP4 Panda

Best,
Peter

  parent reply	other threads:[~2010-06-18 21:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-18 20:42 [U-Boot] [PATCH v3 00/10] Add support for TI OMAP4 SDP and Panda Steve Sakoman
2010-06-18 20:42 ` [U-Boot] [PATCH v3 01/10] ARM: Rename arch/arm/cpu/arm_cortexa8 to armv7 Steve Sakoman
2010-06-18 20:42 ` [U-Boot] [PATCH v3 02/10] ARMV7: Add basic support for TI OMAP4 Steve Sakoman
2010-06-18 20:42 ` [U-Boot] [PATCH v3 03/10] ARMV7: Add support for TI OMAP4430 SDP Steve Sakoman
2010-06-18 20:42 ` [U-Boot] [PATCH v3 04/10] ARMV7: Add support for TI OMAP4 Panda Steve Sakoman
2010-06-18 20:42 ` [U-Boot] [PATCH v3 05/10] ARMV7: Restructure OMAP mmc driver to allow code sharing between OMAP3 and OMAP4 Steve Sakoman
2010-06-18 20:42 ` [U-Boot] [PATCH v3 06/10] ARMV7: Enable mmc support on TI OMAP4430 SDP Steve Sakoman
2010-06-18 20:42 ` [U-Boot] [PATCH v3 07/10] ARMV7: Enable mmc support on TI OMAP4 Panda Steve Sakoman
2010-06-18 20:42 ` [U-Boot] [PATCH v3 08/10] ARMV7: Restructure OMAP i2c driver to allow code sharing between OMAP3 and OMAP4 Steve Sakoman
2010-06-18 20:42 ` [U-Boot] [PATCH v3 09/10] ARMV7: Enable i2c support on TI OMAP4 SDP Steve Sakoman
2010-06-18 20:42 ` [U-Boot] [PATCH v3 10/10] ARMV7: Enable i2c support on TI OMAP4 Panda Steve Sakoman
2010-06-18 21:10 ` Peter Tyser [this message]
2010-06-18 21:53   ` [U-Boot] [PATCH v3 00/10] Add support for TI OMAP4 SDP and Panda Steve Sakoman
2010-06-18 22:19     ` Wolfgang Denk
2010-06-18 22:36       ` Steve Sakoman

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=1276895448.31352.81.camel@petert \
    --to=ptyser@xes-inc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox