public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Kim Phillips <kim.phillips@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 20/31] mpc83xx, kmeter1: extract common I2C options in keymile header
Date: Wed, 28 Jan 2009 20:10:21 -0600	[thread overview]
Message-ID: <20090128201021.a730bede.kim.phillips@freescale.com> (raw)
In-Reply-To: <49802800.3020304@denx.de>

On Wed, 28 Jan 2009 10:40:16 +0100
Heiko Schocher <hs@denx.de> wrote:

> Signed-off-by: Heiko Schocher <hs@denx.de>
> ---
>  include/configs/keymile-common.h |    8 ++++----
>  include/configs/kmeter1.h        |   19 -------------------

a lot of patches in this patchseries touch a lot of the same files -
can you please reorganize the series so that we don't have to review
something that's going to change again in a subsequent patch?

>  2 files changed, 4 insertions(+), 23 deletions(-)
> 
> diff --git a/include/configs/keymile-common.h b/include/configs/keymile-common.h
> index 99c3380..4ff6fb7 100644
> --- a/include/configs/keymile-common.h
> +++ b/include/configs/keymile-common.h
> @@ -42,8 +42,6 @@
>  #define CONFIG_CMD_IMMAP
>  #define CONFIG_CMD_MII
>  #define CONFIG_CMD_PING
> -
> -/* should go away, if kmeter I2C support is enabled */
>  #define CONFIG_CMD_DTT
>  #define CONFIG_CMD_EEPROM
>  #define CONFIG_CMD_I2C

the comment alludes that something should go away yet nothing's going
away but the comment itself.

If there is indeed nothing to take away, then these are the types of
things you need to state why in your commit message.

> @@ -101,7 +99,6 @@
>  #define CONFIG_SYS_SLOT_ID_OFF		(0x07)	/* register offset */
>  #define CONFIG_SYS_SLOT_ID_MASK		(0x3f)	/* mask for slot ID bits */
> 
> -#if defined(CONFIG_MGCOGE) || defined(CONFIG_MGSUVD)
>  #define CONFIG_I2C_MULTI_BUS	1
>  #define CONFIG_I2C_CMD_TREE	1
>  #define CONFIG_SYS_MAX_I2C_BUS		2
> @@ -109,7 +106,11 @@
>  #define CONFIG_I2C_MUX		1
> 
>  /* EEprom support */
> +#if defined(CONFIG_MGCOGE) || defined(CONFIG_MGSUVD)
>  #define CONFIG_SYS_I2C_EEPROM_ADDR_LEN	1
> +#else
> +#define CONFIG_SYS_I2C_EEPROM_ADDR_LEN	2
> +#endif

if this differs per board, shouldn't it be set in the board config, and
not the common config?

Kim

  reply	other threads:[~2009-01-29  2:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-28  9:40 [U-Boot] [PATCH 20/31] mpc83xx, kmeter1: extract common I2C options in keymile header Heiko Schocher
2009-01-29  2:10 ` Kim Phillips [this message]
2009-01-29  9:07   ` Heiko Schocher

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=20090128201021.a730bede.kim.phillips@freescale.com \
    --to=kim.phillips@freescale.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