[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <badd96aa7c475819ed3b9ca48743e10e756b2820.camel@sipsolutions.net>
Date: Tue, 15 Jun 2021 09:31:15 +0200
From: Johannes Berg <johannes@...solutions.net>
To: Sergey Ryazanov <ryazanov.s.a@...il.com>,
Loic Poulain <loic.poulain@...aro.org>,
"David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>
Cc: netdev@...r.kernel.org, M Chetan Kumar <m.chetan.kumar@...el.com>,
Intel Corporation <linuxwwan@...el.com>
Subject: Re: [PATCH net-next 10/10] wwan: core: add WWAN common private data
for netdev
On Tue, 2021-06-15 at 03:30 +0300, Sergey Ryazanov wrote:
> The WWAN core not only multiplex the netdev configuration data, but
> process it too, and needs some space to store its private data
> associated with the netdev. Add a structure to keep common WWAN core
> data. The structure will be stored inside the netdev private data before
> WWAN driver private data and have a field to make it easier to access
> the driver data. Also add a helper function that simplifies drivers
> access to their data.
>
> At the moment we use the common WWAN private data to store the WWAN data
> link (channel) id at the time the link is created, and report it back to
> user using the .fill_info() RTNL callback. This should help the user to
> be aware which network interface is binded to which WWAN device data
Nit: "binded" -> "bound".
> +static size_t wwan_rtnl_get_size(const struct net_device *dev)
> +{
> + return
> + nla_total_size(4) + /* IFLA_WWAN_LINK_ID */
> + 0;
> +}
>
Not sure I like that code style, but I guess I don't care much either :)
johannes
Powered by blists - more mailing lists