From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Guilherme Piccoli <gpiccoli@canonical.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
a.zummo@towertech.it, alexandre.belloni@bootlin.com,
linux-rtc@vger.kernel.org,
"Guilherme G. Piccoli" <kernel@gpiccoli.net>
Subject: Re: [PATCH] rtc: cmos: Don't enable shared interrupts if using HPET-based IRQ handler
Date: Fri, 17 Jan 2020 19:57:56 +0200 [thread overview]
Message-ID: <20200117175756.GV32742@smile.fi.intel.com> (raw)
In-Reply-To: <CAHD1Q_y+9fK_CcmE7VF1XrATQA-Ru9O9=9XyGNvzxwu=Z-q9yQ@mail.gmail.com>
On Fri, Jan 17, 2020 at 11:57:08AM -0300, Guilherme Piccoli wrote:
> On Fri, Jan 17, 2020 at 11:42 AM Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
> > Let me come out with something such as Thomas suggested.
> >
>
> Thank you Andy! In case it's gonna take a while (like more than 1
> kernel release), could we get this one accepted to mitigate the issue
> meanwhile?
I have just sent a series where first patch made to be fix and the rest is
some clean ups.
It would be nice if you can test first patch and series as a whole and
give your Tested-by tags.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2020-01-17 17:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-03 14:02 [PATCH] rtc: cmos: Don't enable shared interrupts if using HPET-based IRQ handler Guilherme G. Piccoli
2020-01-08 17:41 ` Andy Shevchenko
2020-01-08 19:40 ` Thomas Gleixner
2020-01-09 18:27 ` Guilherme G. Piccoli
2020-01-17 10:09 ` Guilherme G. Piccoli
2020-01-17 14:42 ` Andy Shevchenko
2020-01-17 14:57 ` Guilherme Piccoli
2020-01-17 17:57 ` Andy Shevchenko [this message]
2020-01-17 18:01 ` Guilherme Piccoli
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=20200117175756.GV32742@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=gpiccoli@canonical.com \
--cc=kernel@gpiccoli.net \
--cc=linux-rtc@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;
as well as URLs for NNTP newsgroup(s).