From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Alexandre Belloni <alexandre.belloni@free-electrons.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Boris Brezillon <boris.brezillon@free-electrons.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-rt-users@vger.kernel.org>
Subject: Re: [PATCH] clockevents/drivers/timer-atmel-pit: fix double free_irq
Date: Tue, 29 Mar 2016 15:34:54 +0200 [thread overview]
Message-ID: <56FA847E.9080704@atmel.com> (raw)
In-Reply-To: <20160329133206.GA13334@linutronix.de>
Le 29/03/2016 15:32, Sebastian Andrzej Siewior a écrit :
> * Alexandre Belloni | 2016-03-17 21:09:43 [+0100]:
>
>> Hi Sebastian,
> Hi Alexandre,
>
>> This patch fixes the last warning for preempt-rt on at91. It applies on
>> v4.4.4-rt11. Note that the whome PIT/TCB mess will be fixed in another way in
>> the mainline as we are reworking the tcb driver to avoid using the pit when
>> booting.
>
> oh, okay. I just sent the "arm: at91: do not disable/enable clocks in a
> row" patch as you asked me a while ago. It applied cleanly against the
> next tree of today.
Sure, we can still take it now. We will certainly embed it in a future
TC rework.
Thanks.
> So I will apply this to get rid of the warning. And if you manage not to
> use the PIT during boot then we won't have the free_irq() mess which is
> good.
>
> Sebastian
>
--
Nicolas Ferre
next prev parent reply other threads:[~2016-03-29 13:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 20:09 [PATCH] clockevents/drivers/timer-atmel-pit: fix double free_irq Alexandre Belloni
2016-03-18 8:20 ` Nicolas Ferre
2016-03-29 13:32 ` Sebastian Andrzej Siewior
2016-03-29 13:34 ` Nicolas Ferre [this message]
2016-03-29 13:52 ` Alexandre Belloni
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=56FA847E.9080704@atmel.com \
--to=nicolas.ferre@atmel.com \
--cc=alexandre.belloni@free-electrons.com \
--cc=bigeasy@linutronix.de \
--cc=boris.brezillon@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=tglx@linutronix.de \
/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