From: Peter Tyser <ptyser@xes-inc.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [Patch] Disable/Enable Flat I²C Commands
Date: Thu, 29 Jan 2009 14:56:18 -0600 [thread overview]
Message-ID: <1233262578.19784.19.camel@localhost.localdomain> (raw)
In-Reply-To: <20090129203753.624FF832E416@gemini.denx.de>
Hi Wolfgang,
On Thu, 2009-01-29 at 21:37 +0100, Wolfgang Denk wrote:
> Dear Ben Warren,
>
> In message <498203BD.3000500@gmail.com> you wrote:
> >
> > From README:
> >
> >
> > 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 guess this isn't explicit enough. Let's say it gets removed in the
> > release after v2009.03.
>
> Indeed. We should add it to doc/feature_removal.txt and the wiki page.
Its actually already on the wiki page.
http://www.denx.de/wiki/U-Boot/TaskFeatureRemovalSchedule
I submitted the following patch to add it a new
doc/feature-removal-schedule.txt with a similar timeframe:
http://article.gmane.org/gmane.comp.boot-loaders.u-boot/48429
It seems like it would be a good idea to add the
doc/feature_removal.txt. Did the above mentioned patch slip through the
cracks or do you prefer to only use the wiki for feature removals?
Best,
Peter
next prev parent reply other threads:[~2009-01-29 20:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-29 11:46 [U-Boot] [Patch] Disable/Enable Flat I²C Commands Jens Scharsig
2009-01-29 18:16 ` Ben Warren
2009-01-29 18:23 ` Peter Tyser
2009-01-29 19:07 ` Wolfgang Denk
2009-01-29 19:30 ` Ben Warren
2009-01-29 20:37 ` Wolfgang Denk
2009-01-29 20:56 ` Peter Tyser [this message]
2009-01-29 21:04 ` Ben Warren
2009-01-29 21:15 ` Wolfgang Denk
2009-01-29 21:34 ` Peter Tyser
2009-01-29 20:59 ` Ben Warren
2009-01-29 18:52 ` Wolfgang Denk
2009-01-30 7:37 ` Jens Scharsig
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=1233262578.19784.19.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