From: Guenter Roeck <linux@roeck-us.net>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] m68k: mvme: Remove overdue #warnings in RTC handling
Date: Tue, 7 Sep 2021 21:13:02 -0700 [thread overview]
Message-ID: <20210908041302.GA2585571@roeck-us.net> (raw)
In-Reply-To: <20210907124511.2723414-1-geert@linux-m68k.org>
On Tue, Sep 07, 2021 at 02:45:11PM +0200, Geert Uytterhoeven wrote:
> The warnings were introduced when converting the MVME147 and MVME16x
> RTC handling from gettod to hwclk. Replace the #warning by a comment,
> and return an error to inform the upper layer that writing to the RTC is
> not yet supported.
>
> Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
Reviewed-by: Guenter Roeck <linux@roeck-us.net>
> ---
> arch/m68k/mvme147/config.c | 4 +++-
> arch/m68k/mvme16x/config.c | 4 +++-
> 2 files changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/arch/m68k/mvme147/config.c b/arch/m68k/mvme147/config.c
> index e1e90c49a49624cc..dfd6202fd403e92b 100644
> --- a/arch/m68k/mvme147/config.c
> +++ b/arch/m68k/mvme147/config.c
> @@ -171,7 +171,6 @@ static int bcd2int (unsigned char b)
>
> int mvme147_hwclk(int op, struct rtc_time *t)
> {
> -#warning check me!
> if (!op) {
> m147_rtc->ctrl = RTC_READ;
> t->tm_year = bcd2int (m147_rtc->bcd_year);
> @@ -183,6 +182,9 @@ int mvme147_hwclk(int op, struct rtc_time *t)
> m147_rtc->ctrl = 0;
> if (t->tm_year < 70)
> t->tm_year += 100;
> + } else {
> + /* FIXME Setting the time is not yet supported */
> + return -EOPNOTSUPP;
> }
> return 0;
> }
> diff --git a/arch/m68k/mvme16x/config.c b/arch/m68k/mvme16x/config.c
> index b59593c7cfb9dfbf..b4422c2dfbbf4f7c 100644
> --- a/arch/m68k/mvme16x/config.c
> +++ b/arch/m68k/mvme16x/config.c
> @@ -436,7 +436,6 @@ int bcd2int (unsigned char b)
>
> int mvme16x_hwclk(int op, struct rtc_time *t)
> {
> -#warning check me!
> if (!op) {
> rtc->ctrl = RTC_READ;
> t->tm_year = bcd2int (rtc->bcd_year);
> @@ -448,6 +447,9 @@ int mvme16x_hwclk(int op, struct rtc_time *t)
> rtc->ctrl = 0;
> if (t->tm_year < 70)
> t->tm_year += 100;
> + } else {
> + /* FIXME Setting the time is not yet supported */
> + return -EOPNOTSUPP;
> }
> return 0;
> }
> --
> 2.25.1
>
prev parent reply other threads:[~2021-09-08 4:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-07 12:45 [PATCH] m68k: mvme: Remove overdue #warnings in RTC handling Geert Uytterhoeven
2021-09-08 4:13 ` Guenter Roeck [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=20210908041302.GA2585571@roeck-us.net \
--to=linux@roeck-us.net \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.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