From: Hayes Wang <hayeswang@realtek.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [RFC PATCH 0/4] r8169: support dash
Date: Wed, 1 Dec 2021 02:57:00 +0000 [thread overview]
Message-ID: <918d75ea873a453ab2ba588a35d66ab6@realtek.com> (raw)
In-Reply-To: <20211129095947.547a765f@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Jakub Kicinski <kuba@kernel.org>
> Sent: Tuesday, November 30, 2021 2:00 AM
> Subject: Re: [RFC PATCH 0/4] r8169: support dash
>
> On Mon, 29 Nov 2021 18:13:11 +0800 Hayes Wang wrote:
> > These patches are used to support dash for RTL8111EP and
> > RTL8111FP(RTL81117).
>
> If I understand correctly DASH is a DMTF standard for remote control.
>
> Since it's a standard I think we should have a common way of
> configuring it across drivers.
Excuse me. I am not familiar with it.
What document or sample code could I start?
> Is enable/disable the only configuration
> that we will need?
I don't think I could answer it before I understand the above way
you mentioned.
> We don't use sysfs too much these days, can we move the knob to
> devlink, please? (If we only need an on/off switch generic devlink param
> should be fine).
Thanks. I would study devlink.
Best Regards,
Hayes
next prev parent reply other threads:[~2021-12-01 2:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211129101315.16372-381-nic_swsd@realtek.com>
2021-11-29 17:59 ` [Intel-wired-lan] [RFC PATCH 0/4] r8169: support dash Jakub Kicinski
2021-12-01 2:57 ` Hayes Wang [this message]
2021-12-01 3:09 ` Jakub Kicinski
2021-12-03 7:57 ` Hayes Wang
2021-12-03 15:04 ` Jakub Kicinski
2021-12-04 1:08 ` Alexander Lobakin
2021-12-04 1:32 ` Jakub Kicinski
2021-12-07 7:28 ` Hayes Wang
2021-12-08 4:21 ` Jakub Kicinski
2021-12-08 7:53 ` Hayes Wang
2021-12-08 21:37 ` Jakub Kicinski
2021-12-09 7:14 ` Hayes Wang
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=918d75ea873a453ab2ba588a35d66ab6@realtek.com \
--to=hayeswang@realtek.com \
--cc=intel-wired-lan@osuosl.org \
/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