[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b6c5339f0703211117m70d01240mdfe1c0798d3296e2@mail.gmail.com>
Date: Wed, 21 Mar 2007 14:17:42 -0400
From: "Bob Copeland" <me@...copeland.com>
To: bryan.wu@...log.com
Cc: khali@...ux-fr.org, "David Brownell" <david-b@...bell.net>,
"Andrew Morton" <akpm@...ux-foundation.org>,
"Alexey Dobriyan" <adobriyan@...il.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH -mm 4/4] Blackfin: on-chip Two Wire Interface I2C driver
> +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");
-Bob
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists