linux-kernel - Re: pinctrl: core: Handling pinmux and pinconf separately

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: <CACRpkdazxVZCwLK6sJb7-hqhzuWs-HJ=2yiVr-UX4+AoEAWAZw@mail.gmail.com>
Date:   Thu, 11 Mar 2021 15:39:27 +0100
From:   Linus Walleij <linus.walleij@...aro.org>
To:     Michal Simek <michal.simek@...inx.com>
Cc:     Colin Ian King <colin.king@...onical.com>,
        "linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: pinctrl: core: Handling pinmux and pinconf separately

On Thu, Mar 11, 2021 at 12:28 PM Michal Simek <michal.simek@...inx.com> wrote:

> > It will take me 2 hours to re-run the analysis, but from eyeballing the
> > code I think the assignments will fix this.
>
> would be good if you can rerun it and get back to us on this.
> I will wait if something else will pop up and then will send v2 with
> this that Linus can apply this one instead.

Just send an incremental patch, that reflects the issues found
in a nice way in the development history.

Yours,
Linus Walleij