From: Gabriel Paubert <paubert@iram.es>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Wolfgang Denk <wd@denx.de>, Dale Farnsworth <dale@farnsworth.org>,
Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>,
Tom Rini <trini@kernel.crashing.org>
Subject: Re: MPC5200 Patches
Date: Wed, 12 Nov 2003 12:41:14 +0100 [thread overview]
Message-ID: <20031112114114.GA8526@iram.es> (raw)
In-Reply-To: <Pine.GSO.4.21.0311121059070.885-100000@waterleaf.sonytel.be>
On Wed, Nov 12, 2003 at 10:59:59AM +0100, Geert Uytterhoeven wrote:
>
> On Wed, 12 Nov 2003, Wolfgang Denk wrote:
> > In message <Pine.GSO.4.21.0311121029220.885-100000@waterleaf.sonytel.be> you wrote:
> > >
> > > > We have drivers/i2c/i2c-algo-8xx.c, so maybe we should have
> > > > i2c-algo-5xxx.c instead of i2c-algo-m5xxx.c ?
> > > >
> > > > There is include/linux/i2c-algo-8xx.h - how about
> > > > i2c-algo-5xxx.h instead of i2c-algo-m5xxx.h ?
> > ...
> > > What's done in include/asm-ppc/ isn't that important for the
> > > outside (non-PPC) world, but i2c-algo-5xxx.c may be a too generic
> > > name...
> >
> > Which name do you recommend to cover the MGT5100 and MPC5200 (and
> > probably other MPC5xxx) processors?
>
> i2c-algo-m5xxx.c, like the original?
Hmmm, dont't repeated x have a tendency to trigger spam filters
(especially the dumbest ones)?
Why not 5nnn or 5xyz?
Gabriel
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-11-12 11:41 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-01 9:36 MPC5200 Patches Wolfgang Denk
2003-11-03 23:31 ` Dale Farnsworth
2003-11-07 22:20 ` Wolfgang Denk
2003-11-10 19:02 ` Dale Farnsworth
2003-11-10 20:46 ` Wolfgang Denk
2003-11-10 21:00 ` Tom Rini
2003-11-12 0:34 ` Wolfgang Denk
2003-11-12 4:50 ` Dale Farnsworth
2003-11-12 9:30 ` Geert Uytterhoeven
2003-11-12 9:49 ` Wolfgang Denk
2003-11-12 9:59 ` Geert Uytterhoeven
2003-11-12 11:41 ` Gabriel Paubert [this message]
2003-11-12 11:51 ` Geert Uytterhoeven
2003-11-12 14:47 ` Wolfgang Denk
2003-11-12 14:45 ` Wolfgang Denk
2003-11-12 17:43 ` Gabriel Paubert
2003-11-12 19:41 ` Geert Uytterhoeven
2003-11-14 6:11 ` Kumar Gala
2003-11-14 15:20 ` Tom Rini
2003-11-12 15:18 ` Tom Rini
2003-11-12 15:49 ` Gary Thomas
2003-11-12 15:53 ` Tom Rini
2003-11-16 20:33 ` Wolfgang Denk
2003-11-17 6:07 ` Dale Farnsworth
2003-11-17 8:35 ` Wolfgang Denk
2003-11-17 15:19 ` Tom Rini
2003-11-17 16:02 ` Wolfgang Denk
2003-11-17 16:25 ` Tom Rini
2003-11-18 14:52 ` Dale Farnsworth
2003-11-20 11:53 ` Christoph Hellwig
2003-11-20 12:10 ` Wolfgang Denk
2003-11-20 12:17 ` Christoph Hellwig
2003-11-21 1:04 ` Paul Mackerras
2003-11-18 0:43 ` Benjamin Herrenschmidt
2003-11-18 0:44 ` Benjamin Herrenschmidt
2003-11-18 14:45 ` Wolfgang Denk
2003-11-18 15:00 ` Wolfgang Denk
2003-11-17 18:50 ` Tom Rini
2003-12-03 18:28 ` Dale Farnsworth
[not found] ` <20031203185310.19A48C5F5F@atlas.denx.de>
2003-12-04 0:35 ` Dale Farnsworth
[not found] ` <20031110162536.GC8584@ip68-0-152-218.tc.ph.cox.net>
2003-11-10 19:09 ` Dale Farnsworth
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=20031112114114.GA8526@iram.es \
--to=paubert@iram.es \
--cc=dale@farnsworth.org \
--cc=geert@linux-m68k.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=trini@kernel.crashing.org \
--cc=wd@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;
as well as URLs for NNTP newsgroup(s).