From: shawn.guo@freescale.com (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: i.MX: Select HAVE_IMX_SRC for i.MX5 globally
Date: Mon, 19 May 2014 13:25:23 +0800 [thread overview]
Message-ID: <20140519052522.GH10685@dragon> (raw)
In-Reply-To: <1400088614-27280-2-git-send-email-shc_work@mail.ru>
On Wed, May 14, 2014 at 09:30:14PM +0400, Alexander Shiyan wrote:
> No reason to choose a symbol HAVE_IMX_SRC separately for each supported
> i.MX5 CPU, this patch selects this symbol globally for i.MX5.
>
> Signed-off-by: Alexander Shiyan <shc_work@mail.ru>
Applied, thanks.
next prev parent reply other threads:[~2014-05-19 5:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-14 17:30 [PATCH 1/2] ARM: i.MX: Open "Device tree only" Kconfig chapter for non-V7 CPUs Alexander Shiyan
2014-05-14 17:30 ` [PATCH 2/2] ARM: i.MX: Select HAVE_IMX_SRC for i.MX5 globally Alexander Shiyan
2014-05-19 5:25 ` Shawn Guo [this message]
2014-05-19 5:23 ` [PATCH 1/2] ARM: i.MX: Open "Device tree only" Kconfig chapter for non-V7 CPUs 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=20140519052522.GH10685@dragon \
--to=shawn.guo@freescale.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).