linux-kernel - Re: [v5,2/3] i2c: mux: pca954x: support property idle-state

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]

Message-ID: <e04c77cc-6c41-8ce3-b584-944eb1595191@axentia.se>
Date:   Mon, 18 Nov 2019 23:03:53 +0000
From:   Peter Rosin <peda@...ntia.se>
To:     Biwen Li <biwen.li@....com>, Leo Li <leoyang.li@....com>,
        "robh+dt@...nel.org" <robh+dt@...nel.org>,
        "mark.rutland@....com" <mark.rutland@....com>
CC:     "linux-i2c@...r.kernel.org" <linux-i2c@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>
Subject: Re: [v5,2/3] i2c: mux: pca954x: support property idle-state

On 2019-11-15 11:21, Biwen Li wrote:
> Hi Peter,
> 
> Any comments?
> If no comments, could you give me a reviewed-by?

I would have liked a comment from the driver maintainer or a tested-by from
someone with another case than yours. But now that I check I see that there -
contrary to my assumption - is no maintainer listed. So, I think it looks fine,
and I'm sure it compiles cleanly etc if I test that, but I can't test runtime
behavior myself since I don't have the HW. I should have been clearer about
this, and should have double checked the maintainer status instead of relying
on what I thought. I have simply been extremely busy and that slipped. Sorry.

But I'll try to squeeze this into linux-next tomorrow, because if look safe,
and hopefully any problem will become apparent.

Giving a reviewed-by seemed pointless, when I'm the one picking it up :-)

Cheers,
Peter