linux-kernel - Re: [PATCH v9 00/10] mux controller abstraction and iio/i2c muxes

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:   Tue, 28 Feb 2017 16:17:52 +0100
From:   Peter Rosin <peda@...ntia.se>
To:     <linux-kernel@...r.kernel.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Andrew Morton <akpm@...ux-foundation.org>
CC:     Wolfram Sang <wsa@...-dreams.de>, Rob Herring <robh+dt@...nel.org>,
        Mark Rutland <mark.rutland@....com>,
        Jonathan Cameron <jic23@...nel.org>,
        Hartmut Knaack <knaack.h@....de>,
        Lars-Peter Clausen <lars@...afoo.de>,
        Peter Meerwald-Stadler <pmeerw@...erw.net>,
        Jonathan Corbet <corbet@....net>, <linux-i2c@...r.kernel.org>,
        <devicetree@...r.kernel.org>, <linux-iio@...r.kernel.org>,
        <linux-doc@...r.kernel.org>
Subject: Re: [PATCH v9 00/10] mux controller abstraction and iio/i2c muxes

Hi!

The status of this series [1] is that Rob Herring has acked/reviewed all
devicetree changes, so I suppose that's ok. Jonathan Cameron has acked
the additions to the iio subsystem and reviewed the new iio driver.
Wolfram Sang has acked the i2c-mux driver. That's acks or reviews from
the maintainers for all changes to the maintained areas.

What's not covered by the above is the mux subsystem itself. Jonathan
has also acked or reviewed those changes, but I get the feeling that
more tags are desired? So, please review the core of the mux subsystem
and the two drivers! It's small. Really. And much of it is boilerplate
devm functions. The relevant patches are:

 3/10 "mux: minimal mux subsystem and gpio-based mux controller"
10/10 "mux: adg792a: add mux controller driver for ADG792A/G"

I also wonder how I should proceed next. Jonathan kindly provided some
hints. I have created a project on gitlab [2] to track future mux
changes and where this series is also available (in the "mux" branch,
of course subject to rebases, at least for now). I intend to create a
for-next branch that I hope Stephen Rothwell will be happy to add to
linux-next at some point after v4.11-rc1. Whomever I will feed future
changes to will also pull from that tree. Etc. At least that's my
picture of how this is going to work.

The question then becomes to whom I will send pull requests? My guess is
that the plausible candidates are Greg K-H, Linus Torvalds and Andrew
Morton. Any taker? Are there other candidates? I don't have any particular
preference. If I don't hear anything I'll probably just send a pull
request to Linus for the next merge window (i.e. targeting 4.12-rc1).

Or am I perhaps getting ahead of myself? Is a new tree overkill? I
don't expect it to be exactly busy...

Cheers,
peda

[1] https://lkml.org/lkml/2017/2/8/394
[2] https://gitlab.com/peda-linux/mux.git