[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20231009.204104.218796704097737110.fujita.tomonori@gmail.com>
Date: Mon, 09 Oct 2023 20:41:04 +0900 (JST)
From: FUJITA Tomonori <fujita.tomonori@...il.com>
To: jiri@...nulli.us
Cc: fujita.tomonori@...il.com, netdev@...r.kernel.org,
rust-for-linux@...r.kernel.org, andrew@...n.ch,
miguel.ojeda.sandonis@...il.com, greg@...ah.com, tmgross@...ch.edu
Subject: Re: [PATCH net-next v3 3/3] net: phy: add Rust Asix PHY driver
On Mon, 9 Oct 2023 09:23:04 +0200
Jiri Pirko <jiri@...nulli.us> wrote:
>>diff --git a/rust/uapi/uapi_helper.h b/rust/uapi/uapi_helper.h
>>index 301f5207f023..08f5e9334c9e 100644
>>--- a/rust/uapi/uapi_helper.h
>>+++ b/rust/uapi/uapi_helper.h
>>@@ -7,3 +7,5 @@
>> */
>>
>> #include <uapi/asm-generic/ioctl.h>
>>+#include <uapi/linux/mii.h>
>>+#include <uapi/linux/ethtool.h>
>
> What is exactly the reason to change anything in uapi for phy driver?
> Should be just kernel api implementation, no?
It doesn't change anything. Like the C PHY drivers do, Rust PHY
drivers use the defined values in header files in uapi like MII_*,
BMCR_*, etc.
Powered by blists - more mailing lists