From: Pratyush Anand <panand@redhat.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: mingo@kernel.org, alexandre.belloni@free-electrons.com,
rtc-linux@googlegroups.com, linux-kernel@vger.kernel.org,
prarit@redhat.com, Andy Lutomirski <luto@kernel.org>,
Borislav Petkov <bp@suse.de>, "H. Peter Anvin" <hpa@zytor.com>,
Ingo Molnar <mingo@redhat.com>, Jan Beulich <JBeulich@suse.com>,
Viresh Kumar <viresh.kumar@linaro.org>,
"maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<x86@kernel.org>
Subject: Re: [PATCH RFC 1/2] rtc/hpet: Factorize hpet_rtc_timer_init()
Date: Thu, 23 Jun 2016 20:07:13 +0530 [thread overview]
Message-ID: <20160623143713.GB16398@dhcppc9> (raw)
In-Reply-To: <alpine.DEB.2.11.1606231032380.5839@nanos>
Hi Thomas,
On 23/06/2016:10:33:26 AM, Thomas Gleixner wrote:
> On Tue, 21 Jun 2016, Pratyush Anand wrote:
>
> > This patch factorize hpet_rtc_timer_init(), so that counter can be
> > initialized before irq is registered.
>
> This changelog is useless. It tells what the patch does, but not WHY this is
> required.
Sorry, I have described the problem in the cover letter which is here [1].
Please, let me know if any further test/debug result you would need.
Thanks for your help!!
~Pratyush
[1] https://lkml.org/lkml/2016/6/21/35
next prev parent reply other threads:[~2016-06-23 14:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 4:55 [PATCH RFC 0/2] rtc-cmos: Workaround unwanted interrupt generation Pratyush Anand
2016-06-21 4:55 ` [PATCH RFC 1/2] rtc/hpet: Factorize hpet_rtc_timer_init() Pratyush Anand
2016-06-23 8:33 ` Thomas Gleixner
2016-06-23 14:37 ` Pratyush Anand [this message]
2016-06-21 4:55 ` [PATCH RFC 2/2] rtc/rtc-cmos: Initialize software counters before irq is registered Pratyush Anand
2016-06-27 4:49 ` [PATCH RFC 0/2] rtc-cmos: Workaround unwanted interrupt generation Pratyush Anand
2016-07-04 16:19 ` Pratyush Anand
2016-07-18 11:47 ` Pratyush Anand
2016-07-19 14:29 ` Alexandre Belloni
2016-07-20 3:56 ` Pratyush Anand
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=20160623143713.GB16398@dhcppc9 \
--to=panand@redhat.com \
--cc=JBeulich@suse.com \
--cc=alexandre.belloni@free-electrons.com \
--cc=bp@suse.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=prarit@redhat.com \
--cc=rtc-linux@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=viresh.kumar@linaro.org \
--cc=x86@kernel.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