devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Samuel Ortiz <sameo@linux.intel.com>
To: Oleksandr Kozaruk <oleksandr.kozaruk@ti.com>
Cc: tony@atomide.com, lgirdwood@gmail.com, broonie@kernel.org,
	grant.likely@linaro.org, rob.herring@calxeda.com,
	rob@landley.net, t-kristo@ti.com, gg@slimlogic.co.uk,
	linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
	devicetree-discuss@lists.ozlabs.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH] MFD: Change TWL6025 references to TWL6032
Date: Thu, 20 Jun 2013 10:27:41 +0200	[thread overview]
Message-ID: <20130620082741.GB15667@zurbaran> (raw)
In-Reply-To: <1371644642-934-1-git-send-email-oleksandr.kozaruk@ti.com>

Hi Oleksandr,

On Wed, Jun 19, 2013 at 03:24:02PM +0300, Oleksandr Kozaruk wrote:
> From: Graeme Gregory <gg@slimlogic.co.uk>
> 
> The TWL6025 was never released beyond sample form and was replaced by
> the PhoenixLite range of chips - TWL6032. Change the references to
> reference the TWL6032 class and name the registers to twl6032 in line with
> an actual released chip name to avoid confusion.
> 
> Currently there are no users of TWL6025 in the code.
> 
> Signed-off-by: Graeme Gregory <gg@slimlogic.co.uk>
> Signed-off-by: Oleksandr Kozaruk <oleksandr.kozaruk@ti.com>
> Acked-by: Lee Jones <lee.jones@linaro.org>
> 
> ---
> 
> There are non-mainline branches that use twl6032 by its name (for example
> git://git.omapzoom.org/kernel/omap.git). There is intention to add support
> of twl6032 device in mainline, but we'd like to know if we can use twl6032
> instead of twl6025 in our new patches, that we are going to provide.
> Related discussion: https://patchwork.kernel.org/patch/2686331/
> 
>  .../bindings/regulator/twl-regulator.txt           |   26 +++----
>  .../devicetree/bindings/usb/twlxxxx-usb.txt        |    2 +-
>  drivers/mfd/twl-core.c                             |   46 ++++++------
>  drivers/regulator/twl-regulator.c                  |   76 ++++++++++----------
>  drivers/usb/phy/phy-twl6030-usb.c                  |    2 +-
>  include/linux/i2c/twl.h                            |   30 ++++----
>  6 files changed, 91 insertions(+), 91 deletions(-)
Applied to mfd-next, thanks.

Cheers,
Samuel.

-- 
Intel Open Source Technology Centre
http://oss.intel.com/

      parent reply	other threads:[~2013-06-20  8:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-19 12:24 [PATCH] MFD: Change TWL6025 references to TWL6032 Oleksandr Kozaruk
     [not found] ` <1371644642-934-1-git-send-email-oleksandr.kozaruk-l0cyMroinI0@public.gmane.org>
2013-06-19 19:36   ` Mark Brown
2013-06-20  8:27 ` Samuel Ortiz [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=20130620082741.GB15667@zurbaran \
    --to=sameo@linux.intel.com \
    --cc=broonie@kernel.org \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=gg@slimlogic.co.uk \
    --cc=grant.likely@linaro.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=oleksandr.kozaruk@ti.com \
    --cc=rob.herring@calxeda.com \
    --cc=rob@landley.net \
    --cc=t-kristo@ti.com \
    --cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).