From: Brecht Machiels <brecht@mos6581.org>
To: Borislav Petkov <bp@suse.de>
Cc: Adrian Huang <adrianhuang0701@gmail.com>,
Alessandro Zummo <a.zummo@towertech.it>,
Alexandre Belloni <alexandre.belloni@free-electrons.com>,
rtc-linux@googlegroups.com, Thomas Gleixner <tglx@linutronix.de>,
John Stultz <john.stultz@linaro.org>,
Rabin Vincent <rabin.vincent@stericsson.com>,
Nagananda Chumbalkar <nchumbalkar@lenovo.com>,
Adrian Huang <ahuang12@lenovo.com>
Subject: [rtc-linux] Re: [RFC PATCH 1/2] Revert "rtc-cmos: Add an alarm disable quirk"
Date: Mon, 18 May 2015 13:19:20 +0200 [thread overview]
Message-ID: <92F16DED-397D-45B4-987A-491BCCBD0DB4@mos6581.org> (raw)
In-Reply-To: <20150518101744.GF23662@pd.tnic>
Hello,
> On 18 May 2015, at 12:17, Borislav Petkov <bp@suse.de> wrote:
>
> On Fri, May 08, 2015 at 05:34:25PM +0800, Adrian Huang wrote:
>> Commit d5a1c7e3fc38 ("rtc-cmos: Add an alarm disable quirk") that
>> added a special quirk is not needed because PATCH [2/2] of this
>> patchset makes the kernel more robust:
>> rtc: restore the RTC alarm time to the configured alarm time in BIOS
>> Setup
>>
>> Signed-off-by: Adrian Huang <ahuang12@lenovo.com>
>> ---
>> drivers/rtc/rtc-cmos.c | 52 --------------------------------------------------
>> 1 file changed, 52 deletions(-)
>
> ...
>
>> - /* http://permalink.gmane.org/gmane.linux.kernel/1604474 */
>> - {
>> - .callback = set_alarm_disable_quirk,
>> - .ident = "Toshiba Satellite L300",
>> - .matches = {
>> - DMI_MATCH(DMI_SYS_VENDOR, "TOSHIBA"),
>> - DMI_MATCH(DMI_PRODUCT_NAME, "Satellite L300"),
>> - },
>> - },
>
> Looking at the link, this must be Brecht's box.
>
> Brecht, is there any way you could test those patches? I'm attaching
> them here.
No, sorry, I'm no longer running Linux.
Best regards,
Brecht
--
--
You received this message because you are subscribed to "rtc-linux".
Membership options at http://groups.google.com/group/rtc-linux .
Please read http://groups.google.com/group/rtc-linux/web/checklist
before submitting a driver.
---
You received this message because you are subscribed to the Google Groups "rtc-linux" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rtc-linux+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
prev parent reply other threads:[~2015-05-18 11:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-08 9:34 [rtc-linux] [RFC PATCH 1/2] Revert "rtc-cmos: Add an alarm disable quirk" Adrian Huang
2015-05-18 9:47 ` [rtc-linux] " Borislav Petkov
2015-05-18 10:00 ` Diego Ercolani
2015-05-18 10:12 ` Borislav Petkov
2015-05-18 16:01 ` Borislav Petkov
2015-05-21 8:31 ` Diego Ercolani
2015-05-21 20:25 ` Diego Ercolani
2015-05-21 20:52 ` Borislav Petkov
2015-05-21 22:16 ` Egbert Eich
2015-05-21 23:44 ` Huang Adrian
2015-05-22 6:20 ` Diego Ercolani
2015-05-18 10:17 ` Borislav Petkov
2015-05-18 11:19 ` Brecht Machiels [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=92F16DED-397D-45B4-987A-491BCCBD0DB4@mos6581.org \
--to=brecht@mos6581.org \
--cc=a.zummo@towertech.it \
--cc=adrianhuang0701@gmail.com \
--cc=ahuang12@lenovo.com \
--cc=alexandre.belloni@free-electrons.com \
--cc=bp@suse.de \
--cc=john.stultz@linaro.org \
--cc=nchumbalkar@lenovo.com \
--cc=rabin.vincent@stericsson.com \
--cc=rtc-linux@googlegroups.com \
--cc=tglx@linutronix.de \
/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