From: Maxime Ripard <maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
To: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Cc: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 0/5] ARM: sun6i: Switch to enable-method for SMP
Date: Sat, 17 May 2014 18:42:35 +0200 [thread overview]
Message-ID: <20140517164235.GM29258@lukather> (raw)
In-Reply-To: <1397847713-28418-1-git-send-email-maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 380 bytes --]
On Fri, Apr 18, 2014 at 09:01:48PM +0200, Maxime Ripard wrote:
> The recent introduction of CPU_METHOD_OF_DECLARE allowed to deprecate
> one more fiel of the struct machine_desc.
>
> Switch to it for the Allwinner A31 SoC.
Merged the whole series.
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2014-05-17 16:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-18 19:01 [PATCH 0/5] ARM: sun6i: Switch to enable-method for SMP Maxime Ripard
[not found] ` <1397847713-28418-1-git-send-email-maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
2014-04-18 19:01 ` [PATCH 1/5] Documentation: dt: bindings: Document ARM PSCI enable method Maxime Ripard
2014-04-18 19:01 ` [PATCH 2/5] ARM: sun6i: Use CPU_METHOD_OF_DECLARE Maxime Ripard
2014-04-18 19:01 ` [PATCH 3/5] Documentation: dt: bindings: Document Allwinner A31 enable method Maxime Ripard
2014-04-18 19:01 ` [PATCH 4/5] ARM: sun6i: Define the A31 CPUs enable-method Maxime Ripard
2014-04-18 19:01 ` [PATCH 5/5] ARM: sun6i: Retire the smp field in A31 machine Maxime Ripard
2014-05-17 16:42 ` 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=20140517164235.GM29258@lukather \
--to=maxime.ripard-wi1+55scjutkeb57/3fjtnbpr1lh4cv8@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.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 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).