From: Alessandro Zummo <alessandro.zummo@towertech.it>
To: rtc-linux@googlegroups.com
Cc: herton@mandriva.com.br, linux-kernel@vger.kernel.org,
David Brownell <david-b@pacbell.net>
Subject: Re: [rtc-linux] Re: rtc_cmos oops in cmos_rtc_ioctl
Date: Tue, 22 Sep 2009 21:15:46 +0200 [thread overview]
Message-ID: <20090922211546.44c0cf56@i1501.lan.towertech.it> (raw)
In-Reply-To: <200909221515.26777.herton@mandriva.com.br>
On Tue, 22 Sep 2009 15:15:26 -0300
Herton Ronaldo Krzesinski <herton@mandriva.com.br> wrote:
>
> Something like this?:
>
> From a94365843ab40a1904c4bc244af4e551f2f2aca9 Mon Sep 17 00:00:00 2001
> From: Herton Ronaldo Krzesinski <herton@mandriva.com.br>
> Date: Tue, 22 Sep 2009 13:46:00 -0300
> Subject: [PATCH] rtc-cmos: convert RTC_AIE/RTC_UIE to rtc irq API
>
> Drop ioctl function that handles RTC_AIE/RTC_UIE, and use instead the
> rtc subsystem API (alarm_irq_enable/update_irq_enable callbacks).
>
> Signed-off-by: Herton Ronaldo Krzesinski <herton@mandriva.com.br>
Looks nice. David?
> --
> Still, couldn't an oops still trigger with this with dev_set_drvdata after
> rtc_device_register? Lets say, a small test program like this:
dev_set_drvdata should be called before rtc_device_register. I guess
I'll have to patch every single driver :(
[...]
> Compiled and run with similar udev rule. It's very unlikely, and I couldn't
> get an oops anymore unless I moved dev_set_drvdata down in cmos_do_probe in
> my test machine, but should be a possibility?
I don't think so.
--
Best regards,
Alessandro Zummo,
Tower Technologies - Torino, Italy
http://www.towertech.it
next prev parent reply other threads:[~2009-09-22 19:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-21 18:53 rtc_cmos oops in cmos_rtc_ioctl Herton Ronaldo Krzesinski
2009-09-22 10:40 ` Alessandro Zummo
2009-09-22 18:15 ` Herton Ronaldo Krzesinski
2009-09-22 19:15 ` Alessandro Zummo [this message]
2009-09-30 18:59 ` [rtc-linux] " Andrew Morton
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=20090922211546.44c0cf56@i1501.lan.towertech.it \
--to=alessandro.zummo@towertech.it \
--cc=david-b@pacbell.net \
--cc=herton@mandriva.com.br \
--cc=linux-kernel@vger.kernel.org \
--cc=rtc-linux@googlegroups.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