From: festevam@gmail.com (Fabio Estevam)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: mach-mxs: Remove board entries in dt_board_compat
Date: Sun, 17 Jun 2012 11:04:16 -0300 [thread overview]
Message-ID: <1339941856-2836-2-git-send-email-festevam@gmail.com> (raw)
In-Reply-To: <1339941856-2836-1-git-send-email-festevam@gmail.com>
From: Fabio Estevam <fabio.estevam@freescale.com>
There is no need for adding board related entries into dt_board_compat.
Leave only the SoC entry.
This way we do not need to patch a C file when adding dt support for a new board.
Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
---
arch/arm/mach-mxs/mach-mxs.c | 2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/arch/arm/mach-mxs/mach-mxs.c b/arch/arm/mach-mxs/mach-mxs.c
index 8cac94b..0f36b22 100644
--- a/arch/arm/mach-mxs/mach-mxs.c
+++ b/arch/arm/mach-mxs/mach-mxs.c
@@ -91,13 +91,11 @@ static void __init mxs_machine_init(void)
}
static const char *imx23_dt_compat[] __initdata = {
- "fsl,imx23-evk",
"fsl,imx23",
NULL,
};
static const char *imx28_dt_compat[] __initdata = {
- "fsl,imx28-evk",
"fsl,imx28",
NULL,
};
--
1.7.1
next prev parent reply other threads:[~2012-06-17 14:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-17 14:04 [PATCH 1/2] ARM: mach-imx: Remove board entries in dt_board_compat Fabio Estevam
2012-06-17 14:04 ` Fabio Estevam [this message]
2012-06-17 14:06 ` [PATCH 2/2] ARM: mach-mxs: " Marek Vasut
2012-07-05 7:13 ` [PATCH 1/2] ARM: mach-imx: " Sascha Hauer
2012-07-05 7:46 ` Shawn Guo
2012-08-13 15:15 ` Shawn Guo
2012-08-13 15:18 ` Marek Vasut
2012-08-13 21:37 ` Matt Sealey
2012-08-13 16:56 ` Fabio Estevam
2012-08-14 1:28 ` Shawn Guo
2012-08-13 21:48 ` Rob Herring
2012-08-14 1:26 ` 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=1339941856-2836-2-git-send-email-festevam@gmail.com \
--to=festevam@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).