linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oliver Hartkopp <socketcan@hartkopp.net>
To: "Enrico Weigelt, metux IT consult" <lkml@metux.net>,
	Sven Van Asbroeck <thesven73@gmail.com>
Cc: "Linus Walleij" <linus.walleij@linaro.org>,
	"Lee Jones" <lee.jones@linaro.org>,
	mark.rutland@arm.com, "Andreas Färber" <afaerber@suse.de>,
	treding@nvidia.com, "David Lechner" <david@lechnology.com>,
	noralf@tronnes.org, johan@kernel.org,
	"Michal Simek" <monstr@monstr.eu>,
	michal.vokac@ysoft.com, "Arnd Bergmann" <arnd@arndb.de>,
	"Greg KH" <gregkh@linuxfoundation.org>,
	john.garry@huawei.com, geert+renesas@glider.be,
	robin.murphy@arm.com,
	"Paul Gortmaker" <paul.gortmaker@windriver.com>,
	sebastien.bourdelin@savoirfairelinux.com, icenowy@aosc.io,
	"Stuart Yoder" <stuyoder@gmail.com>,
	"J. Kiszka" <jan.kiszka@siemens.com>,
	maxime.ripard@bootlin.com,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH v10 0/7] Add Fieldbus subsystem + support HMS Profinet card
Date: Wed, 24 Apr 2019 12:26:24 +0200	[thread overview]
Message-ID: <06024a8a-ad00-8062-215b-01b2f95a6e24@hartkopp.net> (raw)
In-Reply-To: <e07f7575-2617-a11a-fd78-d068b10a8171@metux.net>

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,
Oliver

  reply	other threads:[~2019-04-24 10:38 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-09 14:42 [PATCH v10 0/7] Add Fieldbus subsystem + support HMS Profinet card Sven Van Asbroeck
2019-04-09 14:42 ` [PATCH v10 1/7] fieldbus_dev: add Fieldbus Device subsystem Sven Van Asbroeck
2019-04-16 11:13   ` Greg KH
2019-04-09 14:42 ` [PATCH v10 2/7] anybus-s: support HMS Anybus-S bus Sven Van Asbroeck
2019-04-09 14:42 ` [PATCH v10 3/7] anybus-s: support the Arcx anybus controller Sven Van Asbroeck
2019-04-09 14:42 ` [PATCH v10 4/7] dt-bindings: anybus-controller: document devicetree binding Sven Van Asbroeck
2019-04-09 15:50   ` Rob Herring
2019-04-09 17:16     ` Sven Van Asbroeck
2019-04-09 17:31       ` Sven Van Asbroeck
2019-04-09 21:09         ` Rob Herring
2019-04-10 13:11           ` Sven Van Asbroeck
2019-04-16 11:11             ` Greg KH
2019-04-09 14:42 ` [PATCH v10 5/7] dt-bindings: Add vendor prefix for arcx / Archronix Sven Van Asbroeck
2019-04-09 14:42 ` [PATCH v10 6/7] fieldbus_dev: support HMS Profinet IRT industrial controller Sven Van Asbroeck
2019-04-09 14:42 ` [PATCH v10 7/7] staging: fieldbus_dev: add TODO Sven Van Asbroeck
2019-04-15 17:41 ` [PATCH v10 0/7] Add Fieldbus subsystem + support HMS Profinet card Enrico Weigelt, metux IT consult
2019-04-15 18:31   ` Sven Van Asbroeck
2019-04-16 16:49     ` Enrico Weigelt, metux IT consult
2019-04-16 18:56       ` Sven Van Asbroeck
2019-04-16 21:18         ` Enrico Weigelt, metux IT consult
2019-04-16 21:49           ` Sven Van Asbroeck
2019-04-16 22:12           ` Sven Van Asbroeck
2019-04-18  8:32             ` Enrico Weigelt, metux IT consult
2019-04-18 17:34               ` Sven Van Asbroeck
2019-04-24  9:40                 ` Enrico Weigelt, metux IT consult
2019-04-24 10:26                   ` Oliver Hartkopp [this message]
2019-04-24 11:00                     ` Andreas Färber
2019-04-24 11:48                       ` Oliver Hartkopp
2019-04-24 15:10                         ` Sven Van Asbroeck
2019-04-29 13:54                           ` Enrico Weigelt, metux IT consult
2019-04-17 14:37           ` Sven Van Asbroeck
2019-04-17 17:04       ` Andreas Färber
2019-04-17 20:13         ` Enrico Weigelt, metux IT consult
2019-04-25  8:26 ` Lee Jones

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=06024a8a-ad00-8062-215b-01b2f95a6e24@hartkopp.net \
    --to=socketcan@hartkopp.net \
    --cc=afaerber@suse.de \
    --cc=arnd@arndb.de \
    --cc=david@lechnology.com \
    --cc=geert+renesas@glider.be \
    --cc=gregkh@linuxfoundation.org \
    --cc=icenowy@aosc.io \
    --cc=jan.kiszka@siemens.com \
    --cc=johan@kernel.org \
    --cc=john.garry@huawei.com \
    --cc=lee.jones@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@metux.net \
    --cc=mark.rutland@arm.com \
    --cc=maxime.ripard@bootlin.com \
    --cc=michal.vokac@ysoft.com \
    --cc=monstr@monstr.eu \
    --cc=netdev@vger.kernel.org \
    --cc=noralf@tronnes.org \
    --cc=paul.gortmaker@windriver.com \
    --cc=robin.murphy@arm.com \
    --cc=sebastien.bourdelin@savoirfairelinux.com \
    --cc=stuyoder@gmail.com \
    --cc=thesven73@gmail.com \
    --cc=treding@nvidia.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).