From: Greg KH <gregkh@linuxfoundation.org>
To: Sven Van Asbroeck <thesven73@gmail.com>
Cc: "Andreas Färber" <afaerber@suse.de>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Enrico Weigelt" <lkml@metux.net>,
"Oliver Hartkopp" <socketcan@hartkopp.net>,
jan.kiszka@siemens.com, "Frank Iwanitz" <friw@hms-networks.de>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH v1 4/5] staging: fieldbus core: add support for FL-NET devices
Date: Mon, 30 Sep 2019 16:07:14 +0200 [thread overview]
Message-ID: <20190930140714.GC2280096@kroah.com> (raw)
In-Reply-To: <20190918183552.28959-5-TheSven73@gmail.com>
On Wed, Sep 18, 2019 at 02:35:51PM -0400, Sven Van Asbroeck wrote:
> Add the FL-NET device type to the fieldbus core.
What does this mean?
>
> Signed-off-by: Sven Van Asbroeck <TheSven73@gmail.com>
> ---
> .../fieldbus/Documentation/ABI/sysfs-class-fieldbus-dev | 1 +
> drivers/staging/fieldbus/dev_core.c | 3 +++
> drivers/staging/fieldbus/fieldbus_dev.h | 1 +
> 3 files changed, 5 insertions(+)
>
> diff --git a/drivers/staging/fieldbus/Documentation/ABI/sysfs-class-fieldbus-dev b/drivers/staging/fieldbus/Documentation/ABI/sysfs-class-fieldbus-dev
> index 439f14d33c3b..233c418016aa 100644
> --- a/drivers/staging/fieldbus/Documentation/ABI/sysfs-class-fieldbus-dev
> +++ b/drivers/staging/fieldbus/Documentation/ABI/sysfs-class-fieldbus-dev
> @@ -12,6 +12,7 @@ Description:
> Possible values:
> 'unknown'
> 'profinet'
> + 'flnet'
>
> What: /sys/class/fieldbus_dev/fieldbus_devX/fieldbus_id
> KernelVersion: 5.1 (staging)
> diff --git a/drivers/staging/fieldbus/dev_core.c b/drivers/staging/fieldbus/dev_core.c
> index 9903c4f3cba9..7e9405e52f19 100644
> --- a/drivers/staging/fieldbus/dev_core.c
> +++ b/drivers/staging/fieldbus/dev_core.c
> @@ -113,6 +113,9 @@ static ssize_t fieldbus_type_show(struct device *dev,
> case FIELDBUS_DEV_TYPE_PROFINET:
> t = "profinet";
> break;
> + case FIELDBUS_DEV_TYPE_FLNET:
> + t = "flnet";
> + break;
> default:
> t = "unknown";
> break;
> diff --git a/drivers/staging/fieldbus/fieldbus_dev.h b/drivers/staging/fieldbus/fieldbus_dev.h
> index 3b00315600e5..f775546b3404 100644
> --- a/drivers/staging/fieldbus/fieldbus_dev.h
> +++ b/drivers/staging/fieldbus/fieldbus_dev.h
> @@ -15,6 +15,7 @@ struct fieldbus_dev_config;
> enum fieldbus_dev_type {
> FIELDBUS_DEV_TYPE_UNKNOWN = 0,
> FIELDBUS_DEV_TYPE_PROFINET,
> + FIELDBUS_DEV_TYPE_FLNET
You add an unspecified enumerated type and suddenly new hardware starts
working? That feels really wrong to me...
greg k-h
next prev parent reply other threads:[~2019-09-30 14:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-18 18:35 [PATCH v1 0/5] Introduce fieldbus_dev configuration interface Sven Van Asbroeck
2019-09-18 18:35 ` [PATCH v1 1/5] staging: fieldbus core: remove unused strings Sven Van Asbroeck
2019-09-18 18:35 ` [PATCH v1 2/5] staging: fieldbus: move "offline mode" definition to fieldbus core Sven Van Asbroeck
2019-09-18 18:35 ` [PATCH v1 3/5] staging: fieldbus core: add support for device configuration Sven Van Asbroeck
2019-09-30 14:06 ` Greg KH
2019-10-02 15:07 ` Sven Van Asbroeck
2019-10-02 15:23 ` Greg KH
2019-10-02 15:43 ` Sven Van Asbroeck
2019-09-18 18:35 ` [PATCH v1 4/5] staging: fieldbus core: add support for FL-NET devices Sven Van Asbroeck
2019-09-30 14:07 ` Greg KH [this message]
2019-10-02 15:08 ` Sven Van Asbroeck
2019-09-18 18:35 ` [PATCH v1 5/5] staging: fieldbus: add support for HMS FL-NET industrial controller Sven Van Asbroeck
2019-09-30 14:05 ` Greg KH
2019-10-02 15:08 ` 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=20190930140714.GC2280096@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=afaerber@suse.de \
--cc=friw@hms-networks.de \
--cc=jan.kiszka@siemens.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@metux.net \
--cc=netdev@vger.kernel.org \
--cc=socketcan@hartkopp.net \
--cc=thesven73@gmail.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).