sparclinux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Finn Thain <fthain@linux-m68k.org>
To: Andreas Larsson <andreas@gaisler.com>,
	 "David S. Miller" <davem@davemloft.net>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	 Alexandre Belloni <alexandre.belloni@bootlin.com>,
	 Daniel Palmer <daniel@0x0f.com>,
	Michael Pavone <pavone@retrodev.com>,
	 linux-kernel@vger.kernel.org, linux-m68k@lists.linux-m68k.org,
	 linux-rtc@vger.kernel.org, sparclinux@vger.kernel.org
Subject: Re: [PATCH v3 0/2] MVME: Adopt standard RTC driver
Date: Wed, 6 Nov 2024 11:03:33 +1100 (AEDT)	[thread overview]
Message-ID: <c1e24cba-69f9-796e-51d7-5c04ad96b75e@linux-m68k.org> (raw)
In-Reply-To: <cover.1728377511.git.fthain@linux-m68k.org>


Hi sparc maintainers

These two patches have now been reviewed by Geert. If you would be so kind 
as to review the sparc changes, I will ask the RTC maintainer to consider 
merging this series.

Regards
Finn

On Tue, 8 Oct 2024, Finn Thain wrote:

> This series removes some duplicated RTC driver code.
> First rtc-m48t59 is tweaked to bring it into equivalence with the RTC
> drivers in arch/m68k/mvme*. Then platform devices are added for the
> former driver and the latter drivers are removed.
> 
> ---
> Changed since v1:
>  - Instead of adding ifdefs to the portable driver, store the year offset
>    in struct m48t59_plat_data.
> 
> Changed since v2:
>  - Use an int for the year offset in struct m48t59_plat_data.
> 
> 
> Finn Thain (2):
>   rtc: m48t59: Use platform_data struct for year offset value
>   m68k: mvme147, mvme16x: Adopt rtc-m48t59 platform driver
> 
>  arch/m68k/configs/multi_defconfig   |   1 +
>  arch/m68k/configs/mvme147_defconfig |   1 +
>  arch/m68k/configs/mvme16x_defconfig |   1 +
>  arch/m68k/include/asm/mvme147hw.h   |  19 +---
>  arch/m68k/include/asm/mvme16xhw.h   |  18 +--
>  arch/m68k/mvme147/config.c          |  55 ++++------
>  arch/m68k/mvme16x/Makefile          |   2 +-
>  arch/m68k/mvme16x/config.c          |  57 ++++------
>  arch/m68k/mvme16x/rtc.c             | 165 ----------------------------
>  arch/sparc/kernel/time_32.c         |   1 +
>  arch/sparc/kernel/time_64.c         |   1 +
>  drivers/rtc/rtc-m48t59.c            |  26 +----
>  include/linux/rtc/m48t59.h          |   3 +
>  13 files changed, 63 insertions(+), 287 deletions(-)
>  delete mode 100644 arch/m68k/mvme16x/rtc.c
> 
> 

      parent reply	other threads:[~2024-11-06  0:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-08  8:51 [PATCH v3 0/2] MVME: Adopt standard RTC driver Finn Thain
2024-10-08  8:51 ` [PATCH v3 1/2] rtc: m48t59: Use platform_data struct for year offset value Finn Thain
2024-10-08  9:19   ` Geert Uytterhoeven
2024-11-06  0:03 ` Finn Thain [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=c1e24cba-69f9-796e-51d7-5c04ad96b75e@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;
as well as URLs for NNTP newsgroup(s).