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: <20210901165736.GA2510553@roeck-us.net>
Date:   Wed, 1 Sep 2021 09:57:36 -0700
From:   Guenter Roeck <linux@...ck-us.net>
To:     Michael Chan <michael.chan@...adcom.com>
Cc:     davem@...emloft.net, netdev@...r.kernel.org, kuba@...nel.org,
        edwin.peer@...adcom.com, gospo@...adcom.com
Subject: Re: [PATCH net-next v2 04/11] bnxt_en: introduce new firmware
 message API based on DMA pools

On Sun, Aug 29, 2021 at 03:34:59AM -0400, Michael Chan wrote:
> From: Edwin Peer <edwin.peer@...adcom.com>
> 
> This change constitutes a major step towards supporting multiple
> firmware commands in flight by maintaining a separate response buffer
> for the duration of each request. These firmware commands are also
> known as Hardware Resource Manager (HWRM) commands.  Using separate
> response buffers requires an API change in order for callers to be
> able to free the buffer when done.
> 

parisc:allmodconfig, and probably others:

drivers/net/ethernet/broadcom/bnxt/bnxt.c: In function 'bnxt_init_board':
drivers/net/ethernet/broadcom/bnxt/bnxt.c:12280:27: error: 'struct bnxt' has no member named 'db_lock'

There is a difference between "#ifdef writeq" and "#if BITS_PER_LONG == 32".

Guenter

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ