From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Ming Lei <tom.leiming@gmail.com>, Tomasz Figa <t.figa@samsung.com>
Cc: linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Kukjin Kim <kgene.kim@samsung.com>,
linux-samsung-soc@vger.kernel.org,
Tomasz Figa <tomasz.figa@gmail.com>
Subject: Re: [PATCH] clockevent: exynos_mct: fix lockdep warning
Date: Fri, 27 Sep 2013 15:17:02 +0200 [thread overview]
Message-ID: <5245854E.5030600@linaro.org> (raw)
In-Reply-To: <CACVXFVO=k-wJ2SrjVQ_k1JhtAOo0-rZ_M780rqGWCbKA8_1qBQ@mail.gmail.com>
On 09/27/2013 03:09 PM, Ming Lei wrote:
> On Thu, Sep 26, 2013 at 6:32 PM, Tomasz Figa <t.figa@samsung.com> wrote:
>>
>> This is a fix that we may want to have, but it must be modified to take
>> my regression fix[1] into account.
>>
>> [1] clocksource: exynos_mct: Set IRQ affinity when the CPU goes online
>> http://thread.gmane.org/gmane.linux.kernel.samsung-soc/22511/focus=23418
>
> OK, I will write and submit v1 against your patch.
Better you stick to
https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git/
or you rebase it against the v3.12-rc3 when it goes out.
Thanks
-- Daniel
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
WARNING: multiple messages have this Message-ID (diff)
From: daniel.lezcano@linaro.org (Daniel Lezcano)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clockevent: exynos_mct: fix lockdep warning
Date: Fri, 27 Sep 2013 15:17:02 +0200 [thread overview]
Message-ID: <5245854E.5030600@linaro.org> (raw)
In-Reply-To: <CACVXFVO=k-wJ2SrjVQ_k1JhtAOo0-rZ_M780rqGWCbKA8_1qBQ@mail.gmail.com>
On 09/27/2013 03:09 PM, Ming Lei wrote:
> On Thu, Sep 26, 2013 at 6:32 PM, Tomasz Figa <t.figa@samsung.com> wrote:
>>
>> This is a fix that we may want to have, but it must be modified to take
>> my regression fix[1] into account.
>>
>> [1] clocksource: exynos_mct: Set IRQ affinity when the CPU goes online
>> http://thread.gmane.org/gmane.linux.kernel.samsung-soc/22511/focus=23418
>
> OK, I will write and submit v1 against your patch.
Better you stick to
https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git/
or you rebase it against the v3.12-rc3 when it goes out.
Thanks
-- Daniel
--
<http://www.linaro.org/> Linaro.org ? Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2013-09-27 13:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-25 14:49 [PATCH] clockevent: exynos_mct: fix lockdep warning Ming Lei
2013-09-25 14:49 ` Ming Lei
2013-09-26 0:39 ` Daniel Lezcano
2013-09-26 0:39 ` Daniel Lezcano
2013-09-26 10:32 ` Tomasz Figa
2013-09-26 10:32 ` Tomasz Figa
2013-09-26 10:54 ` Daniel Lezcano
2013-09-26 10:54 ` Daniel Lezcano
2013-09-27 13:09 ` Ming Lei
2013-09-27 13:09 ` Ming Lei
2013-09-27 13:17 ` Daniel Lezcano [this message]
2013-09-27 13:17 ` Daniel Lezcano
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=5245854E.5030600@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=t.figa@samsung.com \
--cc=tglx@linutronix.de \
--cc=tom.leiming@gmail.com \
--cc=tomasz.figa@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.