[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Ykb7s+uysncYGb0t@lunn.ch>
Date: Fri, 1 Apr 2022 15:18:43 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Simon Horman <simon.horman@...igine.com>
Cc: David Miller <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>, netdev@...r.kernel.org,
oss-drivers@...igine.com,
Niklas Söderlund
<niklas.soderlund@...igine.com>,
Danie du Toit <danie.dutoit@...igine.com>
Subject: Re: [PATCH net] nfp: do not use driver_data to index device info
On Fri, Apr 01, 2022 at 01:19:36PM +0200, Simon Horman wrote:
> From: Niklas Söderlund <niklas.soderlund@...igine.com>
>
> When adding support for multiple chips the struct pci_device_id
> driver_data field was used to hold a index to lookup chip device
> specific information from a table. This works but creates a regressions
> for users who uses /sys/bus/pci/drivers/nfp_netvf/new_id.
>
> For example, before the change writing "19ee 6003" to new_id was
> sufficient but after one needs to write enough fields to be able to also
> match on the driver_data field, "19ee 6003 19ee ffffffff ffffffff 0 1".
>
> The usage of driver_data field was only a convenience and in the belief
> the driver_data field was private to the driver and not exposed in
> anyway to users. Changing the device info lookup to a function that
> translates from struct pci_device_id device field instead works just as
> well and removes the user facing regression.
>
> As a bonus the enum and table with lookup information can be moved out
> from a shared header file to the only file where it's used.
>
> Reported-by: Danie du Toit <danie.dutoit@...igine.com>
> Fixes: e900db704c8512bc ("nfp: parametrize QCP offset/size using dev_info")
> Signed-off-by: Niklas Söderlund <niklas.soderlund@...igine.com>
Hi Simon
This is missing your own Signed-off-by:
Andrew
Powered by blists - more mailing lists