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 13:13:10 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Sven Van Asbroeck <thesven73@...il.com>
Cc:     robh+dt@...nel.org, linus.walleij@...aro.org, lee.jones@...aro.org,
        mark.rutland@....com, afaerber@...e.de, treding@...dia.com,
        david@...hnology.com, noralf@...nnes.org, johan@...nel.org,
        monstr@...str.eu, michal.vokac@...ft.com, arnd@...db.de,
        john.garry@...wei.com, geert+renesas@...der.be,
        robin.murphy@....com, paul.gortmaker@...driver.com,
        sebastien.bourdelin@...oirfairelinux.com, icenowy@...c.io,
        stuyoder@...il.com, jan.kiszka@...mens.com,
        maxime.ripard@...tlin.com, linux-kernel@...r.kernel.org,
        netdev@...r.kernel.org
Subject: Re: [PATCH v10 1/7] fieldbus_dev: add Fieldbus Device subsystem.

On Tue, Apr 09, 2019 at 10:42:44AM -0400, Sven Van Asbroeck wrote:
> Fieldbus device (client) adapters allow data exchange with a PLC aka.
> "Fieldbus Controller" over a fieldbus (Profinet, FLNet, etc.)
> 
> They are typically used when a Linux device wants to expose itself
> as an actuator, motor, console light, switch, etc. over the fieldbus.
> 
> This framework is designed to provide a generic interface to Fieldbus
> Devices from both the Linux Kernel and the userspace.
> 
> Signed-off-by: Sven Van Asbroeck <TheSven73@...il.com>
> ---
>  Documentation/ABI/testing/fieldbus-dev-cdev   |  31 ++
>  .../ABI/testing/sysfs-class-fieldbus-dev      |  62 ++++
>  Documentation/fieldbus_dev/fieldbus_dev.txt   |  66 ++++
>  drivers/staging/Kconfig                       |   2 +
>  drivers/staging/Makefile                      |   1 +
>  drivers/staging/fieldbus/Kconfig              |  19 +
>  drivers/staging/fieldbus/Makefile             |   9 +
>  drivers/staging/fieldbus/dev_core.c           | 349 ++++++++++++++++++
>  include/linux/fieldbus_dev.h                  | 106 ++++++

Please keep all staging code self-contained within your drivers/staging/
directory.

For the dt stuff, as that has been acked, it can go into the "real"
locations.  But for the include and sysfs documentation stuff, that all
needs to stay within your directory.

Can you respin this series based on that and resend?

thanks,

greg k-h

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ