All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shawn Guo <shawnguo@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Fabio Estevam <fabio.estevam@nxp.com>,
	Sascha Hauer <kernel@pengutronix.de>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/6] kill off cpu_is_mx*()
Date: Tue, 28 Jun 2016 10:27:56 +0800	[thread overview]
Message-ID: <20160628022756.GD21328@tiger> (raw)
In-Reply-To: <20160624105001.3166287-1-arnd@arndb.de>

On Fri, Jun 24, 2016 at 12:49:55PM +0200, Arnd Bergmann wrote:
> I noticed that i.MX still uses the traditional cpu_is_* functions to
> tell the difference between various SoC families, but every single
> user of those can be replaced with a simpler way, so we can just
> remove it all.
> 
> Please review and apply for 4.8 if it looks good to you.
> 
> Arnd Bergmann (6):
>   ARM: imx: remove cpu_is_mx1 check
>   ARM: imx: deconstruct mxc_rnga initialization
>   ARM: imx: deconstruct mx3_idle
>   ARM: imx: rework mx27_pm_init() call
>   ARM: imx: remove last call to cpu_is_mx5*
>   ARM: imx: remove cpu_is_mx*()

Thanks for cleaning this up.  Applied all.

Shawn

WARNING: multiple messages have this Message-ID (diff)
From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/6] kill off cpu_is_mx*()
Date: Tue, 28 Jun 2016 10:27:56 +0800	[thread overview]
Message-ID: <20160628022756.GD21328@tiger> (raw)
In-Reply-To: <20160624105001.3166287-1-arnd@arndb.de>

On Fri, Jun 24, 2016 at 12:49:55PM +0200, Arnd Bergmann wrote:
> I noticed that i.MX still uses the traditional cpu_is_* functions to
> tell the difference between various SoC families, but every single
> user of those can be replaced with a simpler way, so we can just
> remove it all.
> 
> Please review and apply for 4.8 if it looks good to you.
> 
> Arnd Bergmann (6):
>   ARM: imx: remove cpu_is_mx1 check
>   ARM: imx: deconstruct mxc_rnga initialization
>   ARM: imx: deconstruct mx3_idle
>   ARM: imx: rework mx27_pm_init() call
>   ARM: imx: remove last call to cpu_is_mx5*
>   ARM: imx: remove cpu_is_mx*()

Thanks for cleaning this up.  Applied all.

Shawn

  parent reply	other threads:[~2016-06-28  2:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-24 10:49 [PATCH 0/6] kill off cpu_is_mx*() Arnd Bergmann
2016-06-24 10:49 ` Arnd Bergmann
2016-06-24 10:49 ` [PATCH 1/6] ARM: imx: remove cpu_is_mx1 check Arnd Bergmann
2016-06-24 10:49   ` Arnd Bergmann
2016-06-24 10:49 ` [PATCH 2/6] ARM: imx: deconstruct mxc_rnga initialization Arnd Bergmann
2016-06-24 10:49   ` Arnd Bergmann
2016-06-24 10:49 ` [PATCH 3/6] ARM: imx: deconstruct mx3_idle Arnd Bergmann
2016-06-24 10:49   ` Arnd Bergmann
2016-06-24 10:49 ` [PATCH 4/6] ARM: imx: rework mx27_pm_init() call Arnd Bergmann
2016-06-24 10:49   ` Arnd Bergmann
2016-06-24 10:50 ` [PATCH 5/6] ARM: imx: remove last call to cpu_is_mx5* Arnd Bergmann
2016-06-24 10:50   ` Arnd Bergmann
2016-06-24 10:50 ` [PATCH 6/6] ARM: imx: remove cpu_is_mx*() Arnd Bergmann
2016-06-24 10:50   ` Arnd Bergmann
2016-06-28  2:27 ` Shawn Guo [this message]
2016-06-28  2:27   ` [PATCH 0/6] kill off cpu_is_mx*() Shawn Guo

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=20160628022756.GD21328@tiger \
    --to=shawnguo@kernel.org \
    --cc=arnd@arndb.de \
    --cc=fabio.estevam@nxp.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    /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.