From: Mian Yousaf Kaukab <ykaukab@suse.de>
To: Bruno Thomsen <bruno.thomsen@gmail.com>
Cc: Alessandro Zummo <a.zummo@towertech.it>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
linux-rtc@vger.kernel.org,
open list <linux-kernel@vger.kernel.org>,
biwen.li@nxp.com
Subject: Re: [PATCH RESEND v4] rtc: pcf2127: handle timestamp interrupts
Date: Thu, 24 Jun 2021 17:22:24 +0200 [thread overview]
Message-ID: <20210624152224.GD81946@suse.de> (raw)
In-Reply-To: <20210624101452.GC81946@suse.de>
On Thu, Jun 24, 2021 at 12:14:52PM +0200, Mian Yousaf Kaukab wrote:
> Second option is to provide support for both cases. Let me know what
> do you prefer.
I have implemented this and I will send it as v5. Please review.
BR,
Yousaf
prev parent reply other threads:[~2021-06-24 15:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-02 10:49 [PATCH RESEND v4] rtc: pcf2127: handle timestamp interrupts Mian Yousaf Kaukab
2021-06-24 6:31 ` Bruno Thomsen
2021-06-24 10:14 ` Mian Yousaf Kaukab
2021-06-24 15:22 ` Mian Yousaf Kaukab [this message]
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=20210624152224.GD81946@suse.de \
--to=ykaukab@suse.de \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=biwen.li@nxp.com \
--cc=bruno.thomsen@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.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;
as well as URLs for NNTP newsgroup(s).