From: Kevin Hilman <khilman@linaro.org>
To: Kumar Gala <galak@codeaurora.org>
Cc: linux-arm-msm <linux-arm-msm@vger.kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/4] arm: qcom: Split Qualcomm support into legacy and multiplatform
Date: Wed, 26 Feb 2014 15:03:10 -0800 [thread overview]
Message-ID: <7hbnxtwk7l.fsf@paris.lan> (raw)
In-Reply-To: <FF42247A-A4E8-4AA2-9C3B-BEEFC2F61714@codeaurora.org> (Kumar Gala's message of "Wed, 26 Feb 2014 11:22:47 -0600")
Kumar Gala <galak@codeaurora.org> writes:
> On Feb 26, 2014, at 8:22 AM, Kevin Hilman <khilman@linaro.org> wrote:
>
>> Kumar Gala <galak@codeaurora.org> writes:
>>
>>> 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>
>>
>> Having a closer look at this after seeing the multi_v7_defconfig change,
>> I have a minor nit on the new ARCH_QCOM name.
>>
>> For new additions, we've been trying to move towards using SOC_foo
>> instead of ARCH_foo. Any reason not to do that here also?
>>
>> Kevin
>
> No reason, just wasn’t aware and no one said anything til now.
Yeah, sorry for not reviewiing sooner.
> Hmm, how to handle this now, can we do this as a 3.16 cleanup?
Yes, we've already merged it, so doing it as a cleanup should be fine.
Thanks,
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: khilman@linaro.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/4] arm: qcom: Split Qualcomm support into legacy and multiplatform
Date: Wed, 26 Feb 2014 15:03:10 -0800 [thread overview]
Message-ID: <7hbnxtwk7l.fsf@paris.lan> (raw)
In-Reply-To: <FF42247A-A4E8-4AA2-9C3B-BEEFC2F61714@codeaurora.org> (Kumar Gala's message of "Wed, 26 Feb 2014 11:22:47 -0600")
Kumar Gala <galak@codeaurora.org> writes:
> On Feb 26, 2014, at 8:22 AM, Kevin Hilman <khilman@linaro.org> wrote:
>
>> Kumar Gala <galak@codeaurora.org> writes:
>>
>>> 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>
>>
>> Having a closer look at this after seeing the multi_v7_defconfig change,
>> I have a minor nit on the new ARCH_QCOM name.
>>
>> For new additions, we've been trying to move towards using SOC_foo
>> instead of ARCH_foo. Any reason not to do that here also?
>>
>> Kevin
>
> No reason, just wasn?t aware and no one said anything til now.
Yeah, sorry for not reviewiing sooner.
> Hmm, how to handle this now, can we do this as a 3.16 cleanup?
Yes, we've already merged it, so doing it as a cleanup should be fine.
Thanks,
Kevin
next prev parent reply other threads:[~2014-02-26 23:03 UTC|newest]
Thread overview: 30+ 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 ` 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 ` Kumar Gala
2014-01-30 18:36 ` [PATCH 2/4] arm: qcom: Split Qualcomm support into legacy and multiplatform Kumar Gala
2014-01-30 18:36 ` Kumar Gala
2014-01-31 19:10 ` Olof Johansson
2014-01-31 19:10 ` Olof Johansson
2014-01-31 19:20 ` Arnd Bergmann
2014-01-31 19:20 ` Arnd Bergmann
2014-01-31 19:25 ` Kumar Gala
2014-01-31 19:25 ` Kumar Gala
2014-01-31 19:34 ` Arnd Bergmann
2014-01-31 19:34 ` Arnd Bergmann
2014-01-31 19:45 ` Kumar Gala
2014-01-31 19:45 ` Kumar Gala
2014-01-31 20:11 ` Rob Herring
2014-01-31 20:11 ` Rob Herring
2014-02-26 14:22 ` Kevin Hilman
2014-02-26 14:22 ` Kevin Hilman
2014-02-26 17:22 ` Kumar Gala
2014-02-26 17:22 ` Kumar Gala
2014-02-26 23:03 ` Kevin Hilman [this message]
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 ` 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
2014-01-31 19:11 ` 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=7hbnxtwk7l.fsf@paris.lan \
--to=khilman@linaro.org \
--cc=galak@codeaurora.org \
--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 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.