From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Finn Thain <fthain@linux-m68k.org>
Cc: "David S. Miller" <davem@davemloft.net>,
Andreas Larsson <andreas@gaisler.com>,
Alexandre Belloni <alexandre.belloni@bootlin.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: [PATCH v3 1/2] rtc: m48t59: Use platform_data struct for year offset value
Date: Tue, 8 Oct 2024 11:19:15 +0200 [thread overview]
Message-ID: <CAMuHMdW7kyLQHc8e6sL7jfQSJJWjkH29M8T7SWCgnKuJyh1xtQ@mail.gmail.com> (raw)
In-Reply-To: <41e9f3f320a70b4d0946f7e0c3622f1dd1e8791c.1728377511.git.fthain@linux-m68k.org>
On Tue, Oct 8, 2024 at 11:01 AM Finn Thain <fthain@linux-m68k.org> wrote:
> Instead of hard-coded values and ifdefs, store the year offset in the
> platform_data struct.
>
> Tested-by: Daniel Palmer <daniel@0x0f.com>
> Signed-off-by: Finn Thain <fthain@linux-m68k.org>
> ---
> I tested this for regressions using qemu-system-sparc64.
> Also, Daniel tested the RTC functionality on his MVME147 system.
>
> Changed since v2:
> - Use an int for the year offset in struct m48t59_plat_data.
Reviewed-by: Geert Uytterhoeven <geert@linux-m68k.org>
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-10-08 9:19 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 [this message]
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=CAMuHMdW7kyLQHc8e6sL7jfQSJJWjkH29M8T7SWCgnKuJyh1xtQ@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=alexandre.belloni@bootlin.com \
--cc=andreas@gaisler.com \
--cc=daniel@0x0f.com \
--cc=davem@davemloft.net \
--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 \
--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).