On Tue, 6 May 2014 00:34:41 +0100 (BST)
"Maciej W. Rozycki" wrote:
> Well, the handling of update-ended interrupts is still missing, as is
> some non-x86 stuff I posted a fix for recently (still pending review, can
> you please look into it sometime?).
Done, sorry for the delay.
--
On Tue, 6 May 2014 00:34:41 +0100 (BST)
Maciej W. Rozycki ma...@linux-mips.org wrote:
Well, the handling of update-ended interrupts is still missing, as is
some non-x86 stuff I posted a fix for recently (still pending review, can
you please look into it sometime?).
Done, sorry for the
On Mon, 28 Apr 2014, Alessandro Zummo wrote:
> > But it sounds like the driver/char/rtc bit is dead code, and needs a
> > cleanup? Or is there some use of that code that you need that the
> > generic RTC layer doesn't have?
>
> as far as I know, no recent distribution is using the old code
On Mon, 28 Apr 2014, Alessandro Zummo wrote:
But it sounds like the driver/char/rtc bit is dead code, and needs a
cleanup? Or is there some use of that code that you need that the
generic RTC layer doesn't have?
as far as I know, no recent distribution is using the old code anymore
On Mon, 2014-04-28 at 20:20 +0200, Alessandro Zummo wrote:
> On Mon, 28 Apr 2014 11:16:37 -0700
> John Stultz wrote:
>
> > >> This breaks the API since there is no more misc device /dev/rtc
> > >> available without a udev rule or a link to /dev/rtc0.
> >
> > So yea.. I feel like that
On Mon, 2014-04-28 at 20:20 +0200, Alessandro Zummo wrote:
On Mon, 28 Apr 2014 11:16:37 -0700
John Stultz john.stu...@linaro.org wrote:
This breaks the API since there is no more misc device /dev/rtc
available without a udev rule or a link to /dev/rtc0.
So yea.. I feel like that
On Mon, 28 Apr 2014 11:16:37 -0700
John Stultz wrote:
> >> This breaks the API since there is no more misc device /dev/rtc
> >> available without a udev rule or a link to /dev/rtc0.
>
> So yea.. I feel like that /dev/rtcN renaming (and API) break (which
> was a huge and annoying pain) was
On Mon, Apr 21, 2014 at 10:58 AM, Randy Dunlap wrote:
> [adding more patch committers]
>
> On 04/13/2014 12:05 PM, Stefani Seibold wrote:
>> Since some kernel version it is impossible to select the Enhanced Real
>> Time Clock Support (legacy PC RTC driver) because RTC_LIB is set by
>> default in
On Mon, Apr 21, 2014 at 10:58 AM, Randy Dunlap rdun...@infradead.org wrote:
[adding more patch committers]
On 04/13/2014 12:05 PM, Stefani Seibold wrote:
Since some kernel version it is impossible to select the Enhanced Real
Time Clock Support (legacy PC RTC driver) because RTC_LIB is set by
On Mon, 28 Apr 2014 11:16:37 -0700
John Stultz john.stu...@linaro.org wrote:
This breaks the API since there is no more misc device /dev/rtc
available without a udev rule or a link to /dev/rtc0.
So yea.. I feel like that /dev/rtcN renaming (and API) break (which
was a huge and annoying
[adding more patch committers]
On 04/13/2014 12:05 PM, Stefani Seibold wrote:
> Since some kernel version it is impossible to select the Enhanced Real
> Time Clock Support (legacy PC RTC driver) because RTC_LIB is set by
> default in arch/x86/Kconfig, but the rule for selecting CONFIG_RTC is
>
[adding more patch committers]
On 04/13/2014 12:05 PM, Stefani Seibold wrote:
Since some kernel version it is impossible to select the Enhanced Real
Time Clock Support (legacy PC RTC driver) because RTC_LIB is set by
default in arch/x86/Kconfig, but the rule for selecting CONFIG_RTC is
Since some kernel version it is impossible to select the Enhanced Real
Time Clock Support (legacy PC RTC driver) because RTC_LIB is set by
default in arch/x86/Kconfig, but the rule for selecting CONFIG_RTC is
RTC_LIB=n. So the code of driver/char/rtc is still useless.
This breaks the API since
Since some kernel version it is impossible to select the Enhanced Real
Time Clock Support (legacy PC RTC driver) because RTC_LIB is set by
default in arch/x86/Kconfig, but the rule for selecting CONFIG_RTC is
RTC_LIB=n. So the code of driver/char/rtc is still useless.
This breaks the API since
14 matches
Mail list logo
