[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bfee014a-617c-49de-9344-b7d511cdf58f@lunn.ch>
Date: Mon, 20 Nov 2023 15:13:23 +0100
From: Andrew Lunn <andrew@...n.ch>
To: FUJITA Tomonori <fujita.tomonori@...il.com>
Cc: benno.lossin@...ton.me, boqun.feng@...il.com, netdev@...r.kernel.org,
rust-for-linux@...r.kernel.org, tmgross@...ch.edu,
miguel.ojeda.sandonis@...il.com, wedsonaf@...il.com
Subject: Re: [PATCH net-next v7 2/5] rust: net::phy add module_phy_driver
macro
> The Rust ax88796b driver doesn't export anything. The Rust and C
> drivers handle the device_table in the same way when they are built as
> a module.
>
> $ grep __mod_mdio /proc/kallsyms
> ffffffffa0358058 r __mod_mdio__phydev_device_table [ax88796b_rust]
>
> $ grep __mod_mdio /proc/kallsyms
> ffffffffa0288010 d __mod_mdio__asix_tbl_device_table [ax88796b]
I checked what r and d mean. If they are upper case, they are
exported. Lower case means they are not exported.
My laptop is using the realtek PHY driver:
0000000000000000 r __mod_mdio__realtek_tbl_device_table [realtek]
Also lower r.
Looking at all the symbols for the realtek driver, all the symbols use
lower case. Nothing is exported.
Is that what you see for the ax88796b_rust?
Andrew
Powered by blists - more mailing lists