From: b-cousson@ti.com (Cousson, Benoit)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/2] I2C: i2c-omap: Change device name: i2c_omap -> omap_i2c
Date: Fri, 10 Dec 2010 09:28:37 +0100 [thread overview]
Message-ID: <4D01E4B5.1010703@ti.com> (raw)
In-Reply-To: <BC214410FD04D84F9079A6242365970707D4FA@008-AM1MPN1-001.mgdnok.nokia.com>
On 12/9/2010 11:18 PM, aaro.koskinen at nokia.com wrote:
> Hi,
>
> Kevin Hilman [khilman at deeprootsystems.com]:
>> Ben Dooks<ben-i2c@fluff.org> writes:
>>> Renaming stuff like this is going to have an impact on the userspace
>>> as anyone looking through /sys's driver heirarchy is going to miss the
>>> old name...
>>>
>>> It all depends if you really want to go ahead with this...
>>
>> Yes, we are aware of the userspace impact, but this name change makes
>> all devices on OMAP have consistent names and actually improves the
>> ability to have userspace tools have consistent naming as well.
>
> So there are no imporant users, or if there is, they are prepared for this change?
Well, I do not know any user of that today. Do you have some in mind?
Benoit
next prev parent reply other threads:[~2010-12-10 8:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-09 14:24 [PATCH v2 0/2] OMAP: I2C and UART device name cleanup Benoit Cousson
2010-12-09 14:24 ` [PATCH v2 1/2] I2C: i2c-omap: Change device name: i2c_omap -> omap_i2c Benoit Cousson
2010-12-09 16:55 ` Kevin Hilman
2010-12-09 19:01 ` Ben Dooks
2010-12-09 20:46 ` Kevin Hilman
2010-12-09 22:18 ` aaro.koskinen at nokia.com
2010-12-09 22:21 ` Ben Dooks
2010-12-09 23:39 ` Ben Dooks
2010-12-10 8:28 ` Cousson, Benoit [this message]
2010-12-18 1:55 ` Tony Lindgren
2010-12-20 16:07 ` Kevin Hilman
2010-12-21 1:34 ` Tony Lindgren
2010-12-09 20:58 ` Ben Dooks
2010-12-09 17:04 ` Paul Walmsley
2010-12-09 14:24 ` [PATCH v2 2/2] OMAP: serial: Change device name: omap-hsuart -> omap_uart Benoit Cousson
2010-12-09 16:56 ` [PATCH v2 0/2] OMAP: I2C and UART device name cleanup Kevin Hilman
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=4D01E4B5.1010703@ti.com \
--to=b-cousson@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).