From: "Sverdlin, Alexander" <alexander.sverdlin@siemens.com>
To: "alexandre.belloni@bootlin.com" <alexandre.belloni@bootlin.com>
Cc: "Stockmann, Lukas" <lukas.stockmann@siemens.com>,
"linux-rtc@vger.kernel.org" <linux-rtc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] rtc: pcf85063: do a SW reset after rtc power fail
Date: Fri, 15 Mar 2024 10:03:41 +0000 [thread overview]
Message-ID: <37524eee0cf4fd550a7338aadef02fff34619902.camel@siemens.com> (raw)
In-Reply-To: <f882d7964d2d905288bcb7d01421b5eb5bd1b6f2.camel@siemens.com>
prev parent reply other threads:[~2024-03-15 10:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 13:14 [PATCH] rtc: pcf85063: do a SW reset after rtc power fail A. Sverdlin
2024-02-29 22:08 ` Alexandre Belloni
2024-03-01 11:10 ` Sverdlin, Alexander
2024-03-15 10:03 ` Sverdlin, Alexander [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=37524eee0cf4fd550a7338aadef02fff34619902.camel@siemens.com \
--to=alexander.sverdlin@siemens.com \
--cc=alexandre.belloni@bootlin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=lukas.stockmann@siemens.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).