From: tony@atomide.com (Tony Lindgren) Date: Mon, 20 Dec 2010 17:34:26 -0800 Subject: [PATCH v2 1/2] I2C: i2c-omap: Change device name: i2c_omap -> omap_i2c In-Reply-To: <87oc8g5sxj.fsf@deeprootsystems.com> References: <1291904657-32729-1-git-send-email-b-cousson@ti.com> <1291904657-32729-2-git-send-email-b-cousson@ti.com> <878vzydgxr.fsf@deeprootsystems.com> <20101209190110.GR20097@trinity.fluff.org> <87wrni7jys.fsf@deeprootsystems.com> <4D01E4B5.1010703@ti.com> <20101218015507.GL5941@atomide.com> <87oc8g5sxj.fsf@deeprootsystems.com> Message-ID: <20101221013426.GJ5941@atomide.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org * Kevin Hilman [101220 08:07]: > Tony Lindgren writes: > > > * Cousson, Benoit [101210 00:29]: > >> On 12/9/2010 11:18 PM, aaro.koskinen at nokia.com wrote: > >> >Hi, > >> > > >> >Kevin Hilman [khilman at deeprootsystems.com]: > >> >>Ben Dooks 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? > > > > Sounds like it's safe for me to take these two. > > These should probably go via Paul's integration branch to avoid > conflicts with the other omap_device/omap_hwmod code. Well Paul acked it.. Will check with him what he wants to do. Tony