From: Kumar Gala <galak@codeaurora.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/4] arm: qcom: Split Qualcomm support into legacy and multiplatform
Date: Fri, 31 Jan 2014 13:25:25 -0600 [thread overview]
Message-ID: <2B2190A4-6689-40D8-A3D7-BD2D882A2CF6@codeaurora.org> (raw)
In-Reply-To: <201401312020.16984.arnd@arndb.de>
On Jan 31, 2014, at 1:20 PM, Arnd Bergmann <arnd@arndb.de> wrote:
> On Thursday 30 January 2014, Kumar Gala wrote:
>> Introduce a new mach-qcom that will support SoCs that intend to be
>> multiplatform compatiable while keeping mach-msm to legacy SoC/board
>> support that will not transition over to multiplatform.
>>
>> As part of this, we move support for MSM8X60, MSM8960 and MSM8974 over
>> to mach-qcom.
>>
>> Signed-off-by: Kumar Gala <galak@codeaurora.org>
>> ---
>> MAINTAINERS | 7 +++
>> arch/arm/Kconfig | 7 +--
>> arch/arm/Makefile | 1 +
>> arch/arm/boot/dts/Makefile | 6 +--
>> arch/arm/mach-msm/Kconfig | 45 +------------------
>> arch/arm/mach-msm/Makefile | 7 ---
>> arch/arm/mach-msm/hotplug.c | 51 ----------------------
>> arch/arm/mach-qcom/Kconfig | 34 +++++++++++++++
>> arch/arm/mach-qcom/Makefile | 5 +++
>> .../arm/{mach-msm/board-dt.c => mach-qcom/board.c} | 9 ++--
>> arch/arm/{mach-msm => mach-qcom}/scm-boot.c | 0
>> arch/arm/{mach-msm => mach-qcom}/scm-boot.h | 0
>> arch/arm/{mach-msm => mach-qcom}/scm.c | 0
>> arch/arm/{mach-msm => mach-qcom}/scm.h | 0
>> arch/arm/{mach-msm/platsmp.c => mach-qcom/smp.c} | 11 ++++-
>
> The hotplug.c change sticks out as something that isn't just a move
> of code to another place, but deletion of unused code. It would
> be nice to split that out into a separate change, possibly together
> with the trivial board.c and smp.c changes.
That’s not 100% true, the hotplug.c code implemented msm_cpu_die, which moved into smp.c
I can split out scm*/smp* into a patch to enable smp if that is really desired, but not exactly sure what it gets us.
- k
--
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
next prev parent reply other threads:[~2014-01-31 19:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 18:36 [PATCH 0/4] Split mach-msm into legacy and mach-qcom (multiplatform) Kumar Gala
2014-01-30 18:36 ` [PATCH 1/4] clocksource: qcom: Move clocksource code out of mach-msm Kumar Gala
2014-01-30 18:36 ` [PATCH 2/4] arm: qcom: Split Qualcomm support into legacy and multiplatform Kumar Gala
2014-01-31 19:10 ` Olof Johansson
2014-01-31 19:20 ` Arnd Bergmann
2014-01-31 19:25 ` Kumar Gala [this message]
2014-01-31 19:34 ` Arnd Bergmann
2014-01-31 19:45 ` Kumar Gala
2014-01-31 20:11 ` Rob Herring
2014-02-26 14:22 ` Kevin Hilman
2014-02-26 17:22 ` Kumar Gala
2014-02-26 23:03 ` Kevin Hilman
2014-01-30 18:36 ` [PATCH 3/4] clocksource: qcom: split building of legacy vs multiplatform support Kumar Gala
2014-01-30 18:36 ` [PATCH 4/4] tty: serial: msm: Enable building msm_serial for ARCH_QCOM Kumar Gala
2014-01-30 22:36 ` Greg Kroah-Hartman
2014-01-31 19:11 ` [PATCH 0/4] Split mach-msm into legacy and mach-qcom (multiplatform) Olof Johansson
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=2B2190A4-6689-40D8-A3D7-BD2D882A2CF6@codeaurora.org \
--to=galak@codeaurora.org \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®