From: jason@lakedaemon.net (Jason Cooper)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 3/5] arm: mvebu: update defconfig with local timer support
Date: Fri, 15 Feb 2013 16:56:40 -0500 [thread overview]
Message-ID: <20130215215640.GI14746@titan.lakedaemon.net> (raw)
In-Reply-To: <1359135165-32108-4-git-send-email-gregory.clement@free-electrons.com>
On Fri, Jan 25, 2013 at 06:32:43PM +0100, Gregory CLEMENT wrote:
> Now that we have support for local timers, enable it by default
>
> Signed-off-by: Gregory CLEMENT <gregory.clement@free-electrons.com>
> ---
> arch/arm/configs/mvebu_defconfig | 1 -
> 1 file changed, 1 deletion(-)
Applied patches 1, 2, and 3 of this series to mvebu/boards. In the
future, please put driver changes first (patch #2) with few if any
dependencies.
In this case, since these patches depended on SMP support added to
mvebu/boards, I had to apply them to mvebu/boards to prevent a circular
dependency.
thx,
Jason.
next prev parent reply other threads:[~2013-02-15 21:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-25 17:32 [PATCH v2 0/5] arm: mvebu: add support for local timer for Armada 370/XP Gregory CLEMENT
2013-01-25 17:32 ` [PATCH v2 1/5] arm: mvebu: Add support for local interrupt Gregory CLEMENT
2013-01-25 17:32 ` [PATCH v2 2/5] clocksource: time-armada-370-xp: add local timer support Gregory CLEMENT
2013-02-15 21:21 ` Jason Cooper
2013-02-15 21:41 ` Gregory CLEMENT
2013-02-15 21:48 ` Jason Cooper
2013-01-25 17:32 ` [PATCH v2 3/5] arm: mvebu: update defconfig with " Gregory CLEMENT
2013-02-15 21:56 ` Jason Cooper [this message]
2013-02-15 22:04 ` Gregory CLEMENT
2013-02-15 22:09 ` Jason Cooper
2013-01-25 17:32 ` [PATCH v2 4/5] arm: mvebu: update DT to support local timers Gregory CLEMENT
2013-02-15 21:59 ` Jason Cooper
2013-01-25 17:32 ` [PATCH v2 5/5] clocksource: update and move armada-370-xp-timer documentation to timer directory Gregory CLEMENT
2013-01-30 19:52 ` [PATCH v2 0/5] arm: mvebu: add support for local timer for Armada 370/XP Jason Cooper
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=20130215215640.GI14746@titan.lakedaemon.net \
--to=jason@lakedaemon.net \
--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