public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Matija Glavinic Pecotic <matija.glavinic-pecotic.ext@nokia.com>
Cc: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
	dave.hansen@linux.intel.com, x86@kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	hpa@zytor.com
Subject: Re: [PATCH v3] x86/rtc: Remove __init for runtime functions
Date: Thu, 24 Nov 2022 19:06:21 +0200	[thread overview]
Message-ID: <Y3+kjSupFGY4jMiX@smile.fi.intel.com> (raw)
In-Reply-To: <af226986-c6ba-5192-4544-b878fd3140c8@nokia.com>

On Thu, Nov 24, 2022 at 05:57:30PM +0100, Matija Glavinic Pecotic wrote:
> set_rtc_noop, get_rtc_noop are used runtime, therefore need init removed.
> Crash was observed on x86 platform where cmos rtc is unused and disabled
> via device tree. Function was triggered from ntp: sync_hw_clock, although
> CONFIG_RTC_SYSTOHC=n, however sync_cmos_clock doesn't honour that.
> 
>   Workqueue: events_power_efficient sync_hw_clock
>   RIP: 0010:set_rtc_noop
>   Call Trace:
>    update_persistent_clock64
>    sync_hw_clock
> 
> Fix by dropping __init and making set/get_rtc_noop available runtime.
> 
> Fixes: c311ed6183f4 ("x86/init: Allow DT configured systems to disable RTC at boot time")
> Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>

Side note: seems you sent this not using `git send-email ...`
(I see my @intel.com rather than @linux.intel.com in the Cc list).

But at least the Cc list looks closer to what MAINTAINERS says.

And you forgot to make it clear that a) it's a resend, by altering
--subject-prefix, and b) mentioning this in the changelog.

-- 
With Best Regards,
Andy Shevchenko



      reply	other threads:[~2022-11-24 17:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-24 16:57 [PATCH v3] x86/rtc: Remove __init for runtime functions Matija Glavinic Pecotic
2022-11-24 17:06 ` Andy Shevchenko [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=Y3+kjSupFGY4jMiX@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matija.glavinic-pecotic.ext@nokia.com \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@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