lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200511.133209.1693822192358543471.davem@davemloft.net>
Date:   Mon, 11 May 2020 13:32:09 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     ecree@...arflare.com
Cc:     linux-net-drivers@...arflare.com, netdev@...r.kernel.org
Subject: Re: [PATCH net-next 0/8] sfc: remove nic_data usage in common code

From: Edward Cree <ecree@...arflare.com>
Date: Mon, 11 May 2020 13:23:55 +0100

> efx->nic_data should only be used from NIC-specific code (i.e. nic_type
>  functions and things they call), in files like ef10[_sriov].c and
>  siena.c.  This series refactors several nic_data usages from common
>  code (mainly in mcdi_filters.c) into nic_type functions, in preparation
>  for the upcoming ef100 driver which will use those functions but have
>  its own struct layout for efx->nic_data distinct from ef10's.
> After this series, one nic_data usage (in ptp.c) remains; it wasn't
>  clear to me how to fix it, and ef100 devices don't yet have PTP support
>  (so the initial ef100 driver will not call that code).

Series applied, thanks.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ