lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 21 Nov 2014 12:04:06 +0000
From:	Dmitry Lavnikevich <D.Lavnikevich@...-solutions.com>
To:	"Opensource [Steve Twiss]" <stwiss.opensource@...semi.com>
CC:	Support Opensource <Support.Opensource@...semi.com>,
	"a.zummo@...ertech.it" <a.zummo@...ertech.it>,
	"rtc-linux@...glegroups.com" <rtc-linux@...glegroups.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] rtc: da9063: Fix ALARM interrupt registration.


> On 20Nov, 2014, at 15:43, Opensource [Steve Twiss] <stwiss.opensource@...semi.com> wrote:
> 
> On 20 November 2014 13:09 Dmitry Lavnikevich wrote:
> [...]
>>> 
>>> da9063-rtc da9063-rtc: Failed to request ALARM IRQ -22: -22
>>> da9063-rtc: probe of da9063-rtc failed with error -22
>> 
>> I have tested this patch on pfla02 board and it was ok. On which
>> board this fail occurred?
> 
> I am using a MCIMX6DL-SDP board -- although I the differences are in
> my code base and not the platform in this case.
> My apologies 
> 
> Regards,
> Steve
> 
> patch follows:
[…]

I see that your code also fixes the issue. And it is more consistent with da9055 implementation.
So there is no need for my fix if yours is already there. Is it already accepted on some mainline branch?
If not then are you going to submit it soon?

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ