netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Enrico Weigelt, metux IT consult" <lkml@metux.net>
To: 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 v11 2/7] anybus-s: support HMS Anybus-S bus
Date: Wed, 24 Apr 2019 12:25:50 +0200	[thread overview]
Message-ID: <32fc1e18-ebd3-3c60-282d-0f8f94cdf5da@metux.net> (raw)
In-Reply-To: <CAGngYiUWnFeHLee5c1=E6gS1mZtL9ferzaTdm0txFaG2wVCxpg@mail.gmail.com>

On 18.04.19 19:44, Sven Van Asbroeck wrote:

> At this point we don't know yet where the API might possibly go.
> It might evolve into something broader that includes IEC61158 as
> just one aspect.

I doubt that, because:

* All the devices (at least those I've seen somewhere) that follow
  semantics similar to IEC61158, are actually IEC61158. (maybe not
  everybody fully spec compatible or some dialects). Because that's
  exactly the industry standard for anything that works on that shared
  process memory model.
* the other fieldbus'es I've mentioned have completely different
  semantics and just fit in here.

Therefore: we should call things exactly what they are. We don't call
grapefruits apples, even though both are round and tend to contain a
lot of sugar.

> If and when we mature and get more users/stakeholders, we can then
> look at changing to more specific naming. Definitely before coming out
> of staging/.

I don't like the idea of name changing *after* this went to mainline
and people are actually using it. At that point, people might even
already written their own drivers, so they'd have to change them, too.

Please let's do that ASAP. It doesn't cost us much at this stage.

> Greg KH has accepted the v11 patch set, so at this stage we can make
> changes only by circulating patches on the mailing list. 

@Greg: is that already in your tree ? What do you think about doing
the name change now ?

> Would you like me to post patches for anybus-s documentation / making the
> regulator optional? Or would you like to have a go at that yourself?

If your patches haven't been taken by in Grek yet, it IMHO would be good
to rework the queue w/ the missing pieces (-> v12). Otherwise separate
patches ontop of the already applied queue probably would be better.


--mtx

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

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

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-16 15:56 [PATCH v11 0/7] Add Fieldbus subsystem + support HMS Profinet card Sven Van Asbroeck
2019-04-16 15:56 ` [PATCH v11 1/7] fieldbus_dev: add Fieldbus Device subsystem Sven Van Asbroeck
2019-04-16 15:56 ` [PATCH v11 2/7] anybus-s: support HMS Anybus-S bus Sven Van Asbroeck
2019-04-16 17:06   ` Enrico Weigelt, metux IT consult
2019-04-16 18:43     ` Sven Van Asbroeck
2019-04-16 20:58       ` Enrico Weigelt, metux IT consult
2019-04-16 22:00         ` Sven Van Asbroeck
2019-04-17 15:25           ` Enrico Weigelt, metux IT consult
2019-04-18 17:44             ` Sven Van Asbroeck
2019-04-24 10:25               ` Enrico Weigelt, metux IT consult [this message]
2019-04-24 13:58                 ` Sven Van Asbroeck
2019-04-16 15:56 ` [PATCH v11 3/7] anybus-s: support the Arcx anybus controller Sven Van Asbroeck
2019-04-16 17:27   ` Enrico Weigelt, metux IT consult
2019-04-16 18:35     ` Sven Van Asbroeck
2019-04-16 21:05       ` Enrico Weigelt, metux IT consult
2019-04-16 21:23         ` Sven Van Asbroeck
2019-04-17  8:39           ` Enrico Weigelt, metux IT consult
2019-04-17 14:17             ` Sven Van Asbroeck
2019-04-18  8:15               ` Enrico Weigelt, metux IT consult
2019-04-18  8:18               ` Enrico Weigelt, metux IT consult
2019-04-18 13:18                 ` Sven Van Asbroeck
2019-04-16 15:56 ` [PATCH v11 4/7] dt-bindings: anybus-controller: document devicetree binding Sven Van Asbroeck
2019-04-16 15:56 ` [PATCH v11 5/7] dt-bindings: Add vendor prefix for arcx / Archronix Sven Van Asbroeck
2019-04-16 15:56 ` [PATCH v11 6/7] fieldbus_dev: support HMS Profinet IRT industrial controller Sven Van Asbroeck
2019-04-16 15:56 ` [PATCH v11 7/7] staging: fieldbus_dev: add TODO Sven Van Asbroeck

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=32fc1e18-ebd3-3c60-282d-0f8f94cdf5da@metux.net \
    --to=lkml@metux.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=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).