public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: maxime.ripard@free-electrons•com (Maxime Ripard)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 2/2] arm: sunxi: rename clock compatible strings
Date: Wed, 27 Mar 2013 21:26:13 +0100	[thread overview]
Message-ID: <515355E5.3020804@free-electrons.com> (raw)
In-Reply-To: <1364351958-14503-3-git-send-email-emilio@elopez.com.ar>

Le 27/03/2013 03:39, Emilio L?pez a ?crit :
> During the introduction of the Allwinner SoC platforms, sunxi was
> initially meant as a generic name for all the variants of the Allwinner
> SoC.
> 
> It was ok at the time of the support of only the A10 and A13 that
> look pretty much the same; but it's beginning to be troublesome with
> the future addition of the Allwinner A31 (sun6i) that is quite
> different, and would introduce some weird logic, where sunxi would
> actually mean in some case sun4i and sun5i but without sun6i...
> 
> Moreover, it makes the compatible strings naming scheme not consistent
> with other architectures, where usually for this kind of compability, we
> just use the oldest SoC name that has this IP, so let's do just this.
> 
> Signed-off-by: Emilio L?pez <emilio@elopez•com.ar>

Applied,
Thanks!

-- 
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      reply	other threads:[~2013-03-27 20:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-27  2:39 [PATCH 0/2] rename sunxi clock compatible strings Emilio López
2013-03-27  2:39 ` [PATCH 1/2] clk: sunxi: rename " Emilio López
2013-03-27  8:40   ` Mike Turquette
2013-03-27  9:30     ` Emilio López
2013-03-27 15:32       ` Mike Turquette
2013-03-27  2:39 ` [PATCH 2/2] arm: sunxi: rename clock " Emilio López
2013-03-27 20:26   ` Maxime Ripard [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=515355E5.3020804@free-electrons.com \
    --to=maxime.ripard@free-electrons$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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