From: Kevin Hilman <khilman@deeprootsystems.com>
To: Benoit Cousson <b-cousson@ti.com>
Cc: paul@pwsan.com, linux-omap@vger.kernel.org
Subject: Re: [PATCH 0/3] OMAP: I2C and UART device name cleanup
Date: Tue, 07 Dec 2010 14:20:57 -0800 [thread overview]
Message-ID: <87pqtdjkc6.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1291632093-18799-1-git-send-email-b-cousson@ti.com> (Benoit Cousson's message of "Mon, 6 Dec 2010 11:41:30 +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 original names.
>
> 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
>
>
> Regards,
> Benoit
>
>
> Benoit Cousson (3):
> OMAP: clock: Change device name in clock nodes: i2c_omap -> omap_i2c
> OMAP: i2c: Change device name: i2c_omap -> omap_i2c
These two should probably be combined, as they cannot work
separately.
> OMAP: serial: Change device name: omap-hsuart -> omap_uart
>
Also, can you Cc linux-arm-kernel when you post updated version?
Thanks,
Kevin
prev parent reply other threads:[~2010-12-07 22:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-06 10:41 [PATCH 0/3] OMAP: I2C and UART device name cleanup Benoit Cousson
2010-12-06 10:41 ` [PATCH 1/3] OMAP: clock: Change device name in clock nodes: i2c_omap -> omap_i2c Benoit Cousson
2010-12-06 10:41 ` [PATCH 2/3] OMAP: i2c: Change device name: " Benoit Cousson
2010-12-06 10:41 ` [PATCH 3/3] OMAP: serial: Change device name: omap-hsuart -> omap_uart Benoit Cousson
2010-12-07 22:20 ` 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=87pqtdjkc6.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=b-cousson@ti.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.