From: Greg KH <gregkh@linuxfoundation.org>
To: Sven Van Asbroeck <thesven73@gmail.com>
Cc: robh+dt@kernel.org, "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>,
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>,
maxime.ripard@bootlin.com,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v8 0/6] Add Fieldbus subsystem + support HMS Profinet card
Date: Mon, 11 Mar 2019 12:13:39 -0700 [thread overview]
Message-ID: <20190311191339.GA5628@kroah.com> (raw)
In-Reply-To: <CAGngYiXZtNcqQ3JGgavBxypo75WtAT7T-X4DQFNWD8kQcifU8g@mail.gmail.com>
On Mon, Mar 11, 2019 at 01:02:34PM -0400, Sven Van Asbroeck wrote:
> On Fri, Feb 8, 2019 at 9:14 AM Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > Well, who wants this code? Who uses it? Find those people and get them
> > to review it. If no one wants it or uses it, that kind of implies that
> > it's not needed :)
>
> We have customers who (will) talk to this ABI from userspace, but they are
> not 'Linux-y' enough to come to the mailing list and meaningfully review
> the userspace ABI.
>
> IMHO the current reality of Fieldbus on Linux is companies rolling their own
> proprietary out-of-tree interfaces and drivers. They do this partly because
> there is no existing community or infrastructure. So there is no incentive
> to be involved with mainline, which could also explain why no-one is commenting
> on this Fieldbus ABI.
>
> Chicken-and-egg problem ?
>
> Greg, could I convince you to take this Fieldbus subsystem in drivers/staging?
> Perhaps its presence may kickstart or seed a Linux Fieldbus community.
> Being in staging/ also means that we can tweak the userspace ABI to our
> heart's content if more people/requirements come in.
>
> If there's been no meaningful activity in, say, one year from now, you may
> decide to send this whole subsystem to /dev/null.
That sounds like a good plan, I'll take that. Want to respin the
patches with the code in drivers/staging/ and I'll be glad to queue them
up after 5.1-rc1 is out.
thanks,
greg k-h
next prev parent reply other threads:[~2019-03-11 19:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-24 20:12 [PATCH v8 0/6] Add Fieldbus subsystem + support HMS Profinet card Sven Van Asbroeck
2019-01-24 20:12 ` [PATCH v8 1/6] fieldbus_dev: add Fieldbus Device subsystem Sven Van Asbroeck
2019-02-08 12:18 ` Greg KH
2019-02-08 16:30 ` Sven Van Asbroeck
2019-02-09 9:11 ` Greg KH
2019-01-24 20:12 ` [PATCH v8 2/6] anybus-s: support HMS Anybus-S bus Sven Van Asbroeck
2019-01-24 20:12 ` [PATCH v8 3/6] anybus-s: support the Arcx anybus controller Sven Van Asbroeck
2019-01-24 20:12 ` [PATCH v8 4/6] dt-bindings: anybus-controller: document devicetree binding Sven Van Asbroeck
2019-01-24 20:12 ` [PATCH v8 5/6] dt-bindings: Add vendor prefix for arcx / Archronix Sven Van Asbroeck
2019-01-24 20:12 ` [PATCH v8 6/6] fieldbus_dev: support HMS Profinet IRT industrial controller Sven Van Asbroeck
2019-02-08 12:19 ` Greg KH
2019-02-06 13:47 ` [PATCH v8 0/6] Add Fieldbus subsystem + support HMS Profinet card Sven Van Asbroeck
2019-02-08 12:19 ` Greg KH
2019-02-08 14:05 ` Sven Van Asbroeck
2019-02-08 14:14 ` Greg KH
2019-03-11 17:02 ` Sven Van Asbroeck
2019-03-11 17:25 ` Andreas Färber
2019-03-11 20:01 ` Sven Van Asbroeck
2019-03-11 19:13 ` Greg KH [this message]
2019-03-11 20:03 ` Sven Van Asbroeck
2019-03-12 17:11 ` Sven Van Asbroeck
2019-03-12 17:13 ` Greg KH
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=20190311191339.GA5628@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=afaerber@suse.de \
--cc=arnd@arndb.de \
--cc=david@lechnology.com \
--cc=geert+renesas@glider.be \
--cc=icenowy@aosc.io \
--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=noralf@tronnes.org \
--cc=paul.gortmaker@windriver.com \
--cc=robh+dt@kernel.org \
--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).