From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: David Kozub <zub@linux.fjfi.cvut.cz>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clockevents/drivers/cs5535: improve resilience to spurious interrupts
Date: Fri, 20 Oct 2017 11:46:32 +0200 [thread overview]
Message-ID: <c0959282-17b2-29f0-c817-281f0e80109e@linaro.org> (raw)
In-Reply-To: <alpine.DEB.2.20.1710201138510.1882@nanos>
On 20/10/2017 11:40, Thomas Gleixner wrote:
> On Fri, 20 Oct 2017, Daniel Lezcano wrote:
>> On 20/10/2017 09:49, David Kozub wrote:
>>
>> And it ends up to the bad commit (assuming there are no compilation
>> broken patches in the process).
>
> I don't think it's worth the trouble for this particular issue. We already
> know that the commit which made the spurious detection weaker. So we just
> add that as Fixes tag and be done with it.
Yes, I'm fine with that.
--
<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:[~2017-10-20 9:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-19 20:57 David Kozub
2017-10-19 22:04 ` Daniel Lezcano
2017-10-19 22:25 ` Thomas Gleixner
2017-10-20 6:46 ` Daniel Lezcano
2017-10-20 7:49 ` David Kozub
2017-10-20 9:35 ` Daniel Lezcano
2017-10-20 9:40 ` Thomas Gleixner
2017-10-20 9:46 ` Daniel Lezcano [this message]
2017-10-20 14:59 ` David Kozub
2017-10-19 22:21 ` Thomas Gleixner
2017-10-20 7:38 ` David Kozub
2017-10-20 8:18 ` Thomas Gleixner
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=c0959282-17b2-29f0-c817-281f0e80109e@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=zub@linux.fjfi.cvut.cz \
/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
all inboxes | Powered by JetHome®