netdev - 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]

Date:   Tue, 16 Apr 2019 22:58:36 +0200
From:   "Enrico Weigelt, metux IT consult" <lkml@...ux.net>
To:     Sven Van Asbroeck <thesven73@...il.com>
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 16.04.19 20:43, Sven Van Asbroeck wrote:

Hi,

> Correct on both points :)
> The author of this proprietary standard (HMS) calls this a bus, but only
> a single card can be connected to a slot. So it's not like pci or usb,
> where you can connect multiple devices to a host.

But this port supports probing ?
(so it's, bit like a single usb port w/o hub ;-))

>> Maybe that deserves a bit more documentation :p
>>
> 
> Sure, I can do that. What would be the best location for this?
> The commit message? The Kconfig blurb? Comments in host.c?
> Somewhere in Documentation/ ?

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.

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


--mtx

-- 
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
info@...ux.net -- +49-151-27565287