All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: linux-rtc@vger.kernel.org, Sascha Hauer <s.hauer@pengutronix.de>
Cc: kernel@pengutronix.de, Alessandro Zummo <a.zummo@towertech.it>
Subject: Re: [PATCH RESEND 0/2] rtc: rv8803 patches
Date: Thu, 9 Feb 2023 23:02:31 +0100	[thread overview]
Message-ID: <167598012662.1651125.13925674123145941600.b4-ty@bootlin.com> (raw)
In-Reply-To: <20221123095527.2771434-1-s.hauer@pengutronix.de>


On Wed, 23 Nov 2022 10:55:25 +0100, Sascha Hauer wrote:
> This series has the remainder of
> https://lore.kernel.org/all/20220426071056.1187235-1-s.hauer@pengutronix.de/
> which was partly applied.
> 
> Alexandre,
> 
> Last time this series was send you asked if this series fixes a problem
> we've really seen to which Ahmad answered:
> 
> [...]

Applied, thanks!

[1/2] include/linux/bcd.h: provide bcd_is_valid() helper
      commit: 19409796578c879a41e88ddbdbce50c19457658d
[2/2] rtc: rv8803: invalidate date/time if alarm time is invalid
      commit: e5c594233fcf1a55a439dec103aa815cdbf392a7

-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

      parent reply	other threads:[~2023-02-09 22:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-23  9:55 [PATCH RESEND 0/2] rtc: rv8803 patches Sascha Hauer
2022-11-23  9:55 ` [PATCH 1/2] include/linux/bcd.h: provide bcd_is_valid() helper Sascha Hauer
2022-11-23  9:55 ` [PATCH 2/2] rtc: rv8803: invalidate date/time if alarm time is invalid Sascha Hauer
2022-12-13 10:08 ` [PATCH RESEND 0/2] rtc: rv8803 patches Marc Kleine-Budde
2023-01-09 14:36 ` Marc Kleine-Budde
2023-01-31  8:19 ` Marc Kleine-Budde
2023-01-31 12:00   ` Alexandre Belloni
2023-02-06 15:18     ` Marc Kleine-Budde
2023-02-09 22:03       ` Alexandre Belloni
2023-02-09 22:02 ` Alexandre Belloni [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=167598012662.1651125.13925674123145941600.b4-ty@bootlin.com \
    --to=alexandre.belloni@bootlin.com \
    --cc=a.zummo@towertech.it \
    --cc=kernel@pengutronix.de \
    --cc=linux-rtc@vger.kernel.org \
    --cc=s.hauer@pengutronix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.