linux-kernel - Re: [PATCH v11 2/7] anybus-s: support HMS Anybus-S 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: <CAGngYiUroMwErLugXeVXwHc37Nm+Bw4Tv5i1VUv8=qVcNbaSQQ@mail.gmail.com>
Date:   Tue, 16 Apr 2019 18:00:03 -0400
From:   Sven Van Asbroeck <thesven73@...il.com>
To:     "Enrico Weigelt, metux IT consult" <lkml@...ux.net>
Cc:     Rob Herring <robh+dt@...nel.org>,
        Linus Walleij <linus.walleij@...aro.org>,
        Lee Jones <lee.jones@...aro.org>, mark.rutland@....com,
        Andreas Färber <afaerber@...e.de>,
        treding@...dia.com, David Lechner <david@...hnology.com>,
        noralf@...nnes.org, johan@...nel.org,
        Michal Simek <monstr@...str.eu>, michal.vokac@...ft.com,
        Arnd Bergmann <arnd@...db.de>,
        Greg KH <gregkh@...uxfoundation.org>, john.garry@...wei.com,
        geert+renesas@...der.be, robin.murphy@....com,
        Paul Gortmaker <paul.gortmaker@...driver.com>,
        sebastien.bourdelin@...oirfairelinux.com, icenowy@...c.io,
        Stuart Yoder <stuyoder@...il.com>,
        "J. Kiszka" <jan.kiszka@...mens.com>, maxime.ripard@...tlin.com,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        netdev <netdev@...r.kernel.org>
Subject: Re: [PATCH v11 2/7] anybus-s: support HMS Anybus-S bus

On Tue, Apr 16, 2019 at 5:02 PM Enrico Weigelt, metux IT consult
<lkml@...ux.net> wrote:
>
> But this port supports probing ?
> (so it's, bit like a single usb port w/o hub ;-))

Yes, that's exactly it.

>
> In the long run, Documentation/ IMHO would be the best place
> (at least for longer explainations).
>
> OTOH, a few more precise words in the commit message would be nice, too.

Ok, sounds like a plan.

>
> I guess that things like introducing new bus types or device classes
> are something that subsystem maintainers wanna be aware of :)
>

fieldbus_dev is a new subsystem.
At first I attempted to mainline the anybus-s drivers with a 'roll-your-own'
userspace API, but the feedback I got was: this userspace API should
really be generic... So this is my attempt to create a generic fieldbus_dev
API !

It's almost certainly insufficient, but it's a start. Ideally, this
should get lots
of review from people in the industry, but response to this patchset has
been underwhelming. That's the reason this is going into staging/.
Hopefully it will create discussion, and a way forward to a more extensive
userspace API. If not, it'll go to /dev/null after a year.