From: Thomas Gleixner <tglx@linutronix.de>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: john.stultz@linaro.org, viresh.kumar@linaro.org,
jacob.jun.pan@linux.intel.com,
LAK <linux-arm-kernel@lists.infradead.org>,
santosh.shilimkar@ti.com, linux-pm@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
linaro-kernel@lists.linaro.org, patches@linaro.org,
rickard.andersson@stericsson.com, vincent.guittot@linaro.org,
linus.walleij@stericsson.com, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH 2/4][V2] time : set broadcast irq affinity
Date: Fri, 8 Mar 2013 08:20:33 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.02.1303080817230.22263@ionos> (raw)
In-Reply-To: <51396B39.3090504@linaro.org>
On Fri, 8 Mar 2013, Daniel Lezcano wrote:
> On 03/06/2013 10:48 AM, Thomas Gleixner wrote:
> I was wondering if it would be possible to take the 3/4 and 4/4
> otherwise the flag dependency will prevent to send those to the
> maintainer's tree until they gain visibility on it.
I can take them with the ack of arm soc folks.
Thanks,
tglx
next prev parent reply other threads:[~2013-03-08 7:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-02 10:10 [PATCH 0/4][V2] time: dynamic irq affinity Daniel Lezcano
2013-03-02 10:10 ` [PATCH 1/4][V2] time : pass broadcast parameter Daniel Lezcano
2013-03-02 10:10 ` [PATCH 2/4][V2] time : set broadcast irq affinity Daniel Lezcano
2013-03-05 20:40 ` Thomas Gleixner
2013-03-06 9:27 ` Daniel Lezcano
2013-03-06 9:48 ` Thomas Gleixner
2013-03-06 12:35 ` Daniel Lezcano
2013-03-08 4:38 ` Daniel Lezcano
2013-03-08 7:20 ` Thomas Gleixner [this message]
2013-03-11 21:00 ` Arnd Bergmann
2013-03-02 10:10 ` [PATCH 3/4][V2] ARM: nomadik: add dynamic irq flag to the timer Daniel Lezcano
2013-03-02 10:10 ` [PATCH 4/4][V2] ARM: timer-sp: Set dynamic irq affinity Daniel Lezcano
2013-03-08 15:28 ` Daniel Lezcano
2013-03-11 16:22 ` Russell King - ARM Linux
2013-03-08 15:17 ` [PATCH 3/4][V2] ARM: nomadik: add dynamic irq flag to the timer Daniel Lezcano
2013-03-08 16:03 ` Thomas Gleixner
2013-03-19 11:42 ` Daniel Lezcano
2013-03-12 11:38 ` Linus Walleij
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=alpine.LFD.2.02.1303080817230.22263@ionos \
--to=tglx@linutronix.de \
--cc=arnd@arndb.de \
--cc=daniel.lezcano@linaro.org \
--cc=jacob.jun.pan@linux.intel.com \
--cc=john.stultz@linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linus.walleij@stericsson.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=patches@linaro.org \
--cc=rickard.andersson@stericsson.com \
--cc=santosh.shilimkar@ti.com \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.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).