From: "Mike Frysinger" <vapier.adi@gmail.com>
To: "Jean Delvare" <khali@linux-fr.org>
Cc: "Bob Copeland" <me@bobcopeland.com>,
bryan.wu@analog.com, "David Brownell" <david-b@pacbell.net>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Alexey Dobriyan" <adobriyan@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -mm 4/4] Blackfin: on-chip Two Wire Interface I2C driver
Date: Thu, 22 Mar 2007 03:13:32 -0400 [thread overview]
Message-ID: <8bd0f97a0703220013h7898e5e6sd97df17705765d57@mail.gmail.com> (raw)
In-Reply-To: <20070322080356.738b7a1e.khali@linux-fr.org>
On 3/22/07, Jean Delvare <khali@linux-fr.org> wrote:
> On Wed, 21 Mar 2007 15:14:29 -0400, Mike Frysinger wrote:
> > On 3/21/07, Bob Copeland <me@bobcopeland.com> wrote:
> > > > +config I2C_BLACKFIN_TWI
> > > > + tristate "Blackfin TWI I2C support"
> > > > + depends on I2C && (BF534 || BF536 || BF537)
> > > > + help
> > > > + This is the TWI I2C device driver for Blackfin 534/536/537.
> > > > + This driver can also be built as a module. If so, the module
> > > > + will be called i2c-bfin-twi.
> > >
> > > Pardon my ignorance, but is there any reason to call it "Blackfin TWI"
> > > as opposed to just "Blackfin" since TWI and I2C mean the same thing?
> > > It lends itself to some redundancies such as:
> > >
> > > > + pr_info("I2C: Blackfin I2C TWI driver\n");
> >
> > it reflects the hardware manual and all public Analog Devices
> > documentation ... the peripheral is always referred to as a "Two Wire
> > Interface that is fully compatible with the I2C standard" since using
> > the "I2C" term is not free
>
> Damn, I hate it when legal idiocy takes the lead on technical clarity :(
i'm with you 100% but it isnt my call to make ;(
-mike
next prev parent reply other threads:[~2007-03-22 7:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-21 10:08 Wu, Bryan
2007-03-21 17:56 ` Jean Delvare
2007-03-21 18:17 ` Bob Copeland
2007-03-21 19:14 ` Mike Frysinger
2007-03-22 7:03 ` Jean Delvare
2007-03-22 7:13 ` Mike Frysinger [this message]
2007-03-21 19:22 ` Jean Delvare
2007-03-22 5:39 ` Mike Frysinger
2007-03-22 7:48 ` Jean Delvare
2007-03-22 8:12 ` Mike Frysinger
2007-03-22 9:24 ` Jean Delvare
2007-03-23 5:46 ` [PATCH -mm try#2] " Wu, Bryan
2007-03-23 7:27 ` Jean Delvare
2007-03-23 7:36 ` Wu, Bryan
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=8bd0f97a0703220013h7898e5e6sd97df17705765d57@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bryan.wu@analog.com \
--cc=david-b@pacbell.net \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=me@bobcopeland.com \
/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
all inboxes | Powered by JetHome®