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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20160421130911.GX29844@piout.net>
Date:	Thu, 21 Apr 2016 15:09:11 +0200
From:	Alexandre Belloni <alexandre.belloni@...e-electrons.com>
To:	Javier Martinez Canillas <javier@....samsung.com>
Cc:	linux-kernel@...r.kernel.org, Rob Herring <robh+dt@...nel.org>,
	linux-samsung-soc@...r.kernel.org,
	Krzysztof Kozlowski <k.kozlowski@...sung.com>,
	rtc-linux@...glegroups.com, devicetree@...r.kernel.org
Subject: Re: [rtc-linux] [PATCH v2] rtc: s3c: Document in binding that only
 s3c6410 needs a src clk

On 21/04/2016 at 08:46:33 -0400, Javier Martinez Canillas wrote :
> Hello Alexandre,
> 
> On 03/28/2016 06:19 PM, Alexandre Belloni wrote:
> > On 15/02/2016 at 11:11:06 -0300, Javier Martinez Canillas wrote :
> >> The S3C binding doc says that the RTC and RTC source clocks are required
> >> but the S3C driver supports different HW IP and only the s3c6410 needs a
> >> source clock.
> >>
> >> Fix the binding explaining that the source clock is only needed for the
> >> s3c6410-rtc compatible controller.
> >>
> >> Reported-by: Krzysztof Kozlowski <k.kozlowski@...sung.com>
> >> Signed-off-by: Javier Martinez Canillas <javier@....samsung.com>
> >> Acked-by: Alexandre Belloni <alexandre.belloni@...e-electrons.com>
> >>
> >> ---
> >> Hello,
> >>
> >> This patch depends on a previous one that was picked by Rob Herring so
> >> this one has to go through his tree again and not through the RTC tree
> >> to avoid conflicts.
> >>
> > 
> > Well, I'm queuing that one in rtc-fixes for 4.6
> > 
> 
> Are you still planning to push this fix for v4.6? I don't see the patch in
> neither v4.6-rc4 nor linux-next.
> 

Well, I was expecting to get more fixes but didn't so I still didn't
send the PR to Linus. I'll do that this week.

thanks for the reminder!

-- 
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ