From: galak@codeaurora.org (Kumar Gala)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1 3/4] ARM: qcom: Add APQ8084-MTP board to mach-qcom
Date: Wed, 21 May 2014 10:18:53 -0500 [thread overview]
Message-ID: <A6B00F86-FFD3-4FEF-B39E-EAA511565B80@codeaurora.org> (raw)
In-Reply-To: <1400684225-21381-4-git-send-email-gdjakov@mm-sol.com>
On May 21, 2014, at 9:57 AM, Georgi Djakov <gdjakov@mm-sol.com> wrote:
> Add board compatibility string to the board machine descriptors.
>
> Signed-off-by: Georgi Djakov <gdjakov@mm-sol.com>
> ---
> arch/arm/mach-qcom/board.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm/mach-qcom/board.c b/arch/arm/mach-qcom/board.c
> index bae617e..ae0a405 100644
> --- a/arch/arm/mach-qcom/board.c
> +++ b/arch/arm/mach-qcom/board.c
> @@ -18,6 +18,7 @@ static const char * const qcom_dt_match[] __initconst = {
> "qcom,msm8660-surf",
> "qcom,msm8960-cdp",
> "qcom,apq8074-dragonboard",
> + "qcom,apq8084-mtp",
> NULL
> };
>
> --
> 1.7.9.5
>
Let?s just make this ?qcom,apq8084? to cover other future apq8084 based boards.
- 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-05-21 15:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-21 14:57 [PATCH v1 0/4] Add Qualcomm APQ8084 SoC support Georgi Djakov
2014-05-21 14:57 ` [PATCH v1 1/4] ARM: dts: qcom: Add " Georgi Djakov
2014-05-21 17:24 ` Stephen Boyd
2014-05-21 20:16 ` Georgi Djakov
2014-05-21 14:57 ` [PATCH v1 2/4] ARM: dts: qcom: Add APQ8084-MTP board support Georgi Djakov
2014-05-21 14:57 ` [PATCH v1 3/4] ARM: qcom: Add APQ8084-MTP board to mach-qcom Georgi Djakov
2014-05-21 15:18 ` Kumar Gala [this message]
2014-05-21 15:39 ` Georgi Djakov
2014-05-21 14:57 ` [PATCH v1 4/4] ARM: debug: qcom: Add APQ8084 DEBUG_LL UART support Georgi Djakov
2014-05-21 15:18 ` Arnd Bergmann
2014-05-21 15:28 ` Ivan T. Ivanov
2014-05-21 19:14 ` Kumar Gala
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=A6B00F86-FFD3-4FEF-B39E-EAA511565B80@codeaurora.org \
--to=galak@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.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