From: Hayes Wang <hayeswang@realtek.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: "hkallweit1@gmail.com" <hkallweit1@gmail.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
nic_swsd <nic_swsd@realtek.com>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>
Subject: RE: [RFC PATCH 0/4] r8169: support dash
Date: Wed, 8 Dec 2021 07:53:28 +0000 [thread overview]
Message-ID: <67d7f6f7b6e84af692bc0a7c4c48bb84@realtek.com> (raw)
In-Reply-To: <20211207202101.3a3a93b0@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Jakub Kicinski <kuba@kernel.org>
> Sent: Wednesday, December 8, 2021 12:21 PM
[...]
> > Could devlink param be used for more than 4 bytes settings?
> > At least the IPv6 address is longer.
>
> We can add a new devlink sub-command and driver callback in that case.
Excuse me. Do you mean someone will add it? Then, I could use it.
Or, I have to add it.
> > Besides, we need the information of SMBIOS which could
> > be 4K ~ 8K bytes data. Is there any way we could transmit
> > it to firmware?
>
> Is structure of that data defined by some DMTF standard?
Yes.
Best Regards,
Hayes
WARNING: multiple messages have this Message-ID (diff)
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, 8 Dec 2021 07:53:28 +0000 [thread overview]
Message-ID: <67d7f6f7b6e84af692bc0a7c4c48bb84@realtek.com> (raw)
In-Reply-To: <20211207202101.3a3a93b0@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Jakub Kicinski <kuba@kernel.org>
> Sent: Wednesday, December 8, 2021 12:21 PM
[...]
> > Could devlink param be used for more than 4 bytes settings?
> > At least the IPv6 address is longer.
>
> We can add a new devlink sub-command and driver callback in that case.
Excuse me. Do you mean someone will add it? Then, I could use it.
Or, I have to add it.
> > Besides, we need the information of SMBIOS which could
> > be 4K ~ 8K bytes data. Is there any way we could transmit
> > it to firmware?
>
> Is structure of that data defined by some DMTF standard?
Yes.
Best Regards,
Hayes
next prev parent reply other threads:[~2021-12-08 7:53 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-29 10:13 [RFC PATCH 0/4] r8169: support dash Hayes Wang
2021-11-29 10:13 ` [RFC PATCH 1/4] r8169: remove the relative code about dash Hayes Wang
2021-11-29 10:13 ` [RFC PATCH 2/4] r8169: add type2 access functions Hayes Wang
2021-11-29 10:13 ` [RFC PATCH 3/4] r8169: support CMAC Hayes Wang
2021-11-29 15:47 ` kernel test robot
2021-11-29 20:46 ` Heiner Kallweit
2021-12-03 7:57 ` Hayes Wang
2021-12-03 11:37 ` Heiner Kallweit
2021-11-29 10:13 ` [RFC PATCH 4/4] r8169: add sysfs for dash Hayes Wang
2021-12-03 15:15 ` Heiner Kallweit
2021-12-07 6:53 ` Hayes Wang
2021-12-07 7:38 ` Heiner Kallweit
2021-12-07 8:20 ` Hayes Wang
2021-11-29 17:59 ` [RFC PATCH 0/4] r8169: support dash Jakub Kicinski
2021-11-29 17:59 ` [Intel-wired-lan] " Jakub Kicinski
2021-12-01 2:57 ` Hayes Wang
2021-12-01 2:57 ` [Intel-wired-lan] " Hayes Wang
2021-12-01 3:09 ` Jakub Kicinski
2021-12-01 3:09 ` [Intel-wired-lan] " Jakub Kicinski
2021-12-03 7:57 ` Hayes Wang
2021-12-03 7:57 ` [Intel-wired-lan] " Hayes Wang
2021-12-03 15:04 ` Jakub Kicinski
2021-12-03 15:04 ` [Intel-wired-lan] " Jakub Kicinski
2021-12-04 1:08 ` Alexander Lobakin
2021-12-04 1:08 ` [Intel-wired-lan] " Alexander Lobakin
2021-12-04 1:32 ` Jakub Kicinski
2021-12-04 1:32 ` [Intel-wired-lan] " Jakub Kicinski
2021-12-07 7:28 ` Hayes Wang
2021-12-07 7:28 ` [Intel-wired-lan] " Hayes Wang
2021-12-08 4:21 ` Jakub Kicinski
2021-12-08 4:21 ` [Intel-wired-lan] " Jakub Kicinski
2021-12-08 7:53 ` Hayes Wang [this message]
2021-12-08 7:53 ` Hayes Wang
2021-12-08 21:37 ` Jakub Kicinski
2021-12-08 21:37 ` [Intel-wired-lan] " Jakub Kicinski
2021-12-09 7:14 ` Hayes Wang
2021-12-09 7:14 ` [Intel-wired-lan] " 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=67d7f6f7b6e84af692bc0a7c4c48bb84@realtek.com \
--to=hayeswang@realtek.com \
--cc=hkallweit1@gmail.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.