public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: Benoit Cousson <b-cousson@ti.com>
Cc: paul@pwsan.com, linux-omap@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/2] OMAP: I2C and UART device name cleanup
Date: Thu, 09 Dec 2010 08:56:20 -0800	[thread overview]
Message-ID: <874oamdgwb.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1291904657-32729-1-git-send-email-b-cousson@ti.com> (Benoit Cousson's message of "Thu, 9 Dec 2010 15:24:15 +0100")

Benoit Cousson <b-cousson@ti.com> writes:

> Hi All,
>
> In order to enforce a little bit of consistency in the omap devices name,
> the convention for omap devices name will be now omap_xxx. All the drivers
> adapted to hwmod will be named like that during the on-going adaptations.
>
> The I2C and UART drivers are already adapted to hwmod but with
> the originals name.
>
> Rename i2c and uart using this convention:
> i2c_omap -> omap_i2c
> omap-hsuart -> omap_uart
>
> Tested on OMAP4 ES2 on Panda / sdp4430. Some more validation will be needed on OMAP2 & 3.
>
> This series is based on Kevin's pm-hwmod-i2c branch and is available here:
> git://gitorious.org/omap-pm/linux.git for_2.6.38/device_name

Acked-by: Kevin Hilman <khilman@deeprootsystems.com>

> Regards,
> Benoit
>
>
> v1
>     http://www.spinics.net/lists/linux-omap/msg41474.html
>     
>     Merge previous patch #1 and #2 as suggested by Kevin to change the driver name 
>     at the same time with the device name in the clockdev.
>
>
> Benoit Cousson (2):
>   I2C: i2c-omap: Change device name: i2c_omap -> omap_i2c
>   OMAP: serial: Change device name: omap-hsuart -> omap_uart
>
>  arch/arm/mach-omap1/clock_data.c              |    6 +++---
>  arch/arm/mach-omap2/clock2420_data.c          |    8 ++++----
>  arch/arm/mach-omap2/clock2430_data.c          |    8 ++++----
>  arch/arm/mach-omap2/clock3xxx_data.c          |   12 ++++++------
>  arch/arm/mach-omap2/clock44xx_data.c          |   16 ++++++++--------
>  arch/arm/plat-omap/i2c.c                      |    2 +-
>  arch/arm/plat-omap/include/plat/omap-serial.h |    2 +-
>  drivers/i2c/busses/i2c-omap.c                 |    4 ++--
>  8 files changed, 29 insertions(+), 29 deletions(-)

      parent reply	other threads:[~2010-12-09 16:56 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
2010-12-09 22:21           ` Ben Dooks
2010-12-09 23:39           ` Ben Dooks
2010-12-10  8:28           ` Cousson, Benoit
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 ` Kevin Hilman [this message]

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=874oamdgwb.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=b-cousson@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.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