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]
Date:   Wed, 22 Jan 2020 07:45:28 -0800
From:   Jakub Kicinski <kuba@...nel.org>
To:     Michal Kalderon <michal.kalderon@...vell.com>
Cc:     <ariel.elior@...vell.com>, <davem@...emloft.net>,
        <netdev@...r.kernel.org>, <linux-rdma@...r.kernel.org>,
        <linux-scsi@...r.kernel.org>
Subject: Re: [PATCH net-next 01/14] qed: FW 8.42.2.0 Internal ram offsets
 modifications

On Wed, 22 Jan 2020 17:26:14 +0200, Michal Kalderon wrote:
> IRO stands for internal RAM offsets. Updating the FW binary produces
> different iro offsets. This file contains the different values,
> and a new representation of the values.
> 
> Signed-off-by: Ariel Elior <ariel.elior@...vell.com>
> Signed-off-by: Michal Kalderon <michal.kalderon@...vell.com>

If you have different offsets depending on FW build - where is the code
that checks the FW version is the one driver expects? At a quick glance
you're not bumping any numbers in this patch..

Powered by blists - more mailing lists