linux-kernel - Re: [PATCH v3 1/2] pinctrl: meson: separate soc drivers

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: <CACRpkdavA_yLJb81K+-q0Bpd5Lt4DqiZyBaDX5xAbEyW-8ROWg@mail.gmail.com>
Date:   Mon, 16 Oct 2017 14:00:33 +0200
From:   Linus Walleij <linus.walleij@...aro.org>
To:     Jerome Brunet <jbrunet@...libre.com>
Cc:     Kevin Hilman <khilman@...libre.com>,
        Carlo Caione <carlo@...one.org>,
        "linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
        "open list:ARM/Amlogic Meson..." <linux-amlogic@...ts.infradead.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 1/2] pinctrl: meson: separate soc drivers

On Thu, Oct 12, 2017 at 2:40 PM, Jerome Brunet <jbrunet@...libre.com> wrote:

> When meson pinctrl is enabled, all meson platforms pinctrl drivers are
> built in the kernel, with a significant amount of data.
>
> This leads to situation where pinctrl drivers targeting an architecture
> are also compiled and shipped on another one (ex: meson8 - ARM - compiled
> and shipped on ARM64 builds). This is a waste of memory we can easily
> avoid.
>
> This change makes 4 pinctrl drivers (1 per SoC) out the original single
> driver, allowing to compile and ship only the ones required.
>
> Reviewed-by: Neil Armstrong <narmstrong@...libre.com>
> Reviewed-by: Kevin Hilman <khilman@...libre.com>
> Signed-off-by: Jerome Brunet <jbrunet@...libre.com>

Patch applied.

Yours,
Linus Walleij