mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Finn Thain <fthain@linux-m68k.org>
To: Alexandre Belloni <alexandre.belloni@bootlin.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	 "David S. Miller" <davem@davemloft.net>,
	 Andreas Larsson <andreas@gaisler.com>,
	Daniel Palmer <daniel@0x0f.com>,
	 Michael Pavone <pavone@retrodev.com>,
	linux-m68k@lists.linux-m68k.org,  linux-rtc@vger.kernel.org,
	sparclinux@vger.kernel.org,  linux-kernel@vger.kernel.org
Subject: Re: (subset) [PATCH v4 1/2] rtc: m48t59: Use platform_data struct for year offset value
Date: Thu, 21 Nov 2024 09:13:32 +1100 (AEDT)	[thread overview]
Message-ID: <8140c873-3456-1469-8bc5-2e94d409cf8a@linux-m68k.org> (raw)
In-Reply-To: <173193673970.37302.12055966881506116157.b4-ty@bootlin.com>


On Mon, 18 Nov 2024, Alexandre Belloni wrote:

> On Wed, 13 Nov 2024 09:32:15 +1100, Finn Thain wrote:
> > Instead of hard-coded values and ifdefs, store the year offset in the
> > platform_data struct.
> > 
> > 
> 
> Applied, thanks!
> 
> [1/2] rtc: m48t59: Use platform_data struct for year offset value
>       https://git.kernel.org/abelloni/c/a06e4a93067c
> 

Thanks, Alexandre. Would you also take patch 2/2, please? Geert has sent a 
reviewed-by tag for that one too.

  reply	other threads:[~2024-11-20 22:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-12 22:32 [PATCH v4 0/2] MVME: Adopt standard RTC driver Finn Thain
2024-11-12 22:32 ` [PATCH v4 2/2] m68k: mvme147, mvme16x: Adopt rtc-m48t59 platform driver Finn Thain
2024-11-22 14:44   ` Geert Uytterhoeven
2024-11-22 23:03     ` Alexandre Belloni
2024-11-24  9:42       ` Geert Uytterhoeven
2024-11-12 22:32 ` [PATCH v4 1/2] rtc: m48t59: Use platform_data struct for year offset value Finn Thain
2024-11-15 15:49   ` Andreas Larsson
2024-11-18 13:32   ` (subset) " Alexandre Belloni
2024-11-20 22:13     ` Finn Thain [this message]
2024-11-21 17:46       ` Alexandre Belloni
2024-11-21 18:52         ` Geert Uytterhoeven
2024-11-21 22:24         ` Finn Thain

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=8140c873-3456-1469-8bc5-2e94d409cf8a@linux-m68k.org \
    --to=fthain@linux-m68k.org \
    --cc=alexandre.belloni@bootlin.com \
    --cc=andreas@gaisler.com \
    --cc=daniel@0x0f.com \
    --cc=davem@davemloft.net \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=linux-rtc@vger.kernel.org \
    --cc=pavone@retrodev.com \
    --cc=sparclinux@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
all inboxes | Powered by JetHome®