From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Finn Thain <fthain@linux-m68k.org>
Cc: Daniel Palmer <daniel@0x0f.com>,
Michael Pavone <pavone@retrodev.com>,
linux-m68k@lists.linux-m68k.org, linux-rtc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/2] m68k: mvme147, mvme16x: Adopt rtc-m48t59 platform driver
Date: Mon, 11 Nov 2024 10:27:26 +0100 [thread overview]
Message-ID: <CAMuHMdU45SmMZ+OGn9yS9rrFThESAsFu5Leb_kNVueffM3o_4A@mail.gmail.com> (raw)
In-Reply-To: <a912689ee714d35c13f4a5fe05df58c662a6dc8d.1728377511.git.fthain@linux-m68k.org>
Hi Finn,
On Tue, Oct 8, 2024 at 10:55 AM Finn Thain <fthain@linux-m68k.org> wrote:
> Both mvme147 and mvme16x platforms have their own RTC driver
> implementations that duplicate functionality provided by the rtc-m48t59
> driver. Adopt the rtc-m48t59 driver and remove the other ones.
>
> Tested-by: Daniel Palmer <daniel@0x0f.com>
> Signed-off-by: Finn Thain <fthain@linux-m68k.org>
> ---
> This patch depends upon the m48t59 driver changes in the preceding patch.
>
> Changed since v1:
> - Initialize yy_offset in struct m48t59_plat_data.
> --- a/arch/m68k/configs/multi_defconfig
> +++ b/arch/m68k/configs/multi_defconfig
> @@ -506,6 +506,7 @@ CONFIG_RTC_CLASS=y
> CONFIG_RTC_DRV_MSM6242=m
> CONFIG_RTC_DRV_RP5C01=m
> CONFIG_RTC_DRV_GENERIC=m
> +CONFIG_RTC_DRV_M48T59=m
> # CONFIG_VIRTIO_MENU is not set
> # CONFIG_VHOST_MENU is not set
> # CONFIG_IOMMU_SUPPORT is not set
> diff --git a/arch/m68k/configs/mvme147_defconfig b/arch/m68k/configs/mvme147_defconfig
> index 2248db426081..4a0928b3b842 100644
> --- a/arch/m68k/configs/mvme147_defconfig
> +++ b/arch/m68k/configs/mvme147_defconfig
> @@ -392,6 +392,7 @@ CONFIG_UHID=m
> CONFIG_RTC_CLASS=y
> # CONFIG_RTC_NVMEM is not set
> CONFIG_RTC_DRV_GENERIC=m
> +CONFIG_RTC_DRV_M48T59=y
> # CONFIG_VIRTIO_MENU is not set
> # CONFIG_VHOST_MENU is not set
> # CONFIG_IOMMU_SUPPORT is not set
> diff --git a/arch/m68k/configs/mvme16x_defconfig b/arch/m68k/configs/mvme16x_defconfig
> index 2975b66521f6..481fb2810f1e 100644
> --- a/arch/m68k/configs/mvme16x_defconfig
> +++ b/arch/m68k/configs/mvme16x_defconfig
> @@ -393,6 +393,7 @@ CONFIG_UHID=m
> CONFIG_RTC_CLASS=y
> # CONFIG_RTC_NVMEM is not set
> CONFIG_RTC_DRV_GENERIC=m
> +CONFIG_RTC_DRV_M48T59=y
> # CONFIG_VIRTIO_MENU is not set
> # CONFIG_VHOST_MENU is not set
> # CONFIG_IOMMU_SUPPORT is not set
All of the above don't seem to be inserted at the right location?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2024-11-11 9:27 UTC|newest]
Thread overview: 7+ 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 2/2] m68k: mvme147, mvme16x: Adopt rtc-m48t59 platform driver Finn Thain
2024-11-05 14:21 ` Geert Uytterhoeven
2024-11-11 9:27 ` Geert Uytterhoeven [this message]
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 ` [PATCH v3 0/2] MVME: Adopt standard RTC driver 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=CAMuHMdU45SmMZ+OGn9yS9rrFThESAsFu5Leb_kNVueffM3o_4A@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=daniel@0x0f.com \
--cc=fthain@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 \
/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).