linux-kernel - Re: [PATCH v3 bus+gpio 5/5] dt-bindings: gpio: Document GPIOs via Moxtet bus

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: <CACRpkdYqRzRSdu+xhO2NAt7NYovvkxoE6SCJCq5_UqfD4bY-zg@mail.gmail.com>
Date:   Mon, 4 Mar 2019 10:53:26 +0100
From:   Linus Walleij <linus.walleij@...aro.org>
To:     Marek Behun <marek.behun@....cz>
Cc:     Tony Lindgren <tony@...mide.com>, Shawn Guo <shawnguo@...nel.org>,
        "open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Rob Herring <robh+dt@...nel.org>,
        "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
        <devicetree@...r.kernel.org>
Subject: Re: [PATCH v3 bus+gpio 5/5] dt-bindings: gpio: Document GPIOs via
 Moxtet bus

On Mon, Mar 4, 2019 at 12:17 AM Marek Behun <marek.behun@....cz> wrote:

> do you know who is responsible for merging into drivers/bus?

Usually the ARM SoC maintainers arm@...nel.org merge drivers
there. You should just send them a pull request and explain the
situation I think. Else they know who should deal with it.

Yours,
Linus Walleij