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] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 4 May 2017 00:27:46 +0200
From:   Alexandre Belloni <alexandre.belloni@...e-electrons.com>
To:     Fabio Estevam <festevam@...il.com>
Cc:     Shawn Guo <shawnguo@...nel.org>,
        Gary Bisson <gary.bisson@...ndarydevices.com>,
        Fabio Estevam <fabio.estevam@....com>,
        "linux-arm-kernel@...ts.infradead.org" 
        <linux-arm-kernel@...ts.infradead.org>,
        Sascha Hauer <kernel@...gutronix.de>,
        linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/3] ARM: dts: imx6qdl-nitrogen6_max: fix rv4162
 compatible

On 03/05/2017 at 19:14:42 -0300, Fabio Estevam wrote:
> Hi Shawn,
> 
> On Wed, May 3, 2017 at 5:50 AM, Shawn Guo <shawnguo@...nel.org> wrote:
> 
> >>       rtc: rtc@68 {
> >> -             compatible = "st,rv4162";
> >> +             compatible = "microcrystal,rv4162";
> >
> > The compatible is not documented?
> 
> This compatible has been added in a897bf138c9b443 ("rtc: m41t80: Add
> proper compatible for rv4162") in linux-next, so it will be present in
> 4.12-rc1.

Yes, and to be clear, both patches are independent and can be applied
in any order because the iéC core will still continue to match the
i2c_device_ids if the compatible doesn't match.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ