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] cmd_i2c: Update available commands when	CONFIG_I2C_CMD_TREE is defined
Date: Tue, 14 Oct 2008 15:50:54 -0500	[thread overview]
Message-ID: <1224017454.18428.178.camel@localhost.localdomain> (raw)
In-Reply-To: <20081014203817.B9F7581C99CC@gemini.denx.de>

Hello Wolfgang,

> In message <1222883937-2640-1-git-send-email-ptyser@xes-inc.com> you wrote:
> > If CONFIG_I2C_CMD_TREE is defined, individual i2c commands such as
> > 'imd', 'imm', 'imw', etc should not be available as their functionality
> > is duplicated in the 'i2c' command.
> 
> If I remember correctly, there has been discussion to keep both
> variants in parallel for some transition time.
> 
> I have added a link to your patch to the Feature Removal page at
> http://www.denx.de/wiki/U-Boot/TaskFeatureRemovalSchedule
> so we will not forget this as soon as e have a formal Feature Removal
> file in place.
> 
> Is this OK with you?

According to the top-level README file since at least U-Boot v1.1.5:
"CONFIG_I2C_CMD_TREE is a recommended option that places
all I2C commands under a single 'i2c' root command.  The
older 'imm', 'imd', 'iprobe' etc. commands are considered
deprecated and may disappear in the future."

I personally think that the 2 year warning the README gave is sufficient
but don't have a strong preference if this feature is removed now or at
a later date.  Either way, I think the task feature removal schedule in
general is a great idea.

Best,
Peter

  reply	other threads:[~2008-10-14 20:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-01 17:58 [U-Boot] [PATCH] cmd_i2c: Update available commands when CONFIG_I2C_CMD_TREE is defined Peter Tyser
2008-10-14 20:38 ` Wolfgang Denk
2008-10-14 20:50   ` Peter Tyser [this message]
2008-10-14 21:54     ` Wolfgang Denk
2008-10-15  3:41     ` Ben Warren

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=1224017454.18428.178.camel@localhost.localdomain \
    --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