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:   Wed, 24 Apr 2019 12:26:24 +0200
From:   Oliver Hartkopp <>
To:     "Enrico Weigelt, metux IT consult" <>,
        Sven Van Asbroeck <>
Cc:     Linus Walleij <>,
        Lee Jones <>,,
        Andreas Färber <>,, David Lechner <>,,,
        Michal Simek <>,,
        Arnd Bergmann <>,
        Greg KH <>,,,,
        Paul Gortmaker <>,,,
        Stuart Yoder <>,
        "J. Kiszka" <>,,
        Linux Kernel Mailing List <>,
        netdev <>
Subject: Re: [PATCH v10 0/7] Add Fieldbus subsystem + support HMS Profinet

Thanks Enrico!

On 24.04.19 11:40, Enrico Weigelt, metux IT consult wrote:
> On 18.04.19 19:34, Sven Van Asbroeck wrote:
>> If you have a fieldbus device you want to add to mainline Linux, and> you wish to piggy-back onto the fieldbus_dev subsystem, then we can>
> discuss fieldbus API changes/additions/improvements during the> patch
> review stage.
> With those cases, piggy-backing wouldn't make much sense, as their
> semantics is pretty different.
> My whole point here was just that it shouldn't be called "fieldbus",
> but iec61158 instead.

Full ACK!

The Controller Area Network also belongs to the class of field busses 
and has its own networking subsystem in linux/net/can.

So using a 'class' of communication protocols as naming scheme doesn't 
fit IMHO.

Best regards,

Powered by blists - more mailing lists