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] [day] [month] [year] [list]
Date:   Fri, 12 Mar 2021 16:00:00 +0100
From:   Thomas Bogendoerfer <tsbogend@...ha.franken.de>
To:     Rafał Miłecki <zajec5@...il.com>
Cc:     linux-mips@...r.kernel.org,
        Florian Fainelli <f.fainelli@...il.com>,
        Vivek Unune <npcomplete13@...il.com>,
        bcm-kernel-feedback-list@...adcom.com,
        linux-kernel@...r.kernel.org,
        Philippe Mathieu-Daudé <f4bug@...at.org>,
        Rafał Miłecki <rafal@...ecki.pl>
Subject: Re: [PATCH  mips/linux.git 0/5] firmware: bcm47xx_nvram: refactor
 finding & reading NVRAM

On Mon, Mar 08, 2021 at 10:03:15AM +0100, Rafał Miłecki wrote:
> From: Rafał Miłecki <rafal@...ecki.pl>
> 
> This patchset refactors driver part finding and reading NVRAM.
> 
> It been tested on BCM4706. Updated code checks the same offsets as
> before. Driver still finds & copies NVRAM content.
> 
> It's a new patchset replacing previous single-patch attempt:
> [PATCH V2 mips/linux.git] firmware: bcm47xx_nvram: refactor finding & reading NVRAM
> 
> Rafał Miłecki (5):
>   firmware: bcm47xx_nvram: rename finding function and its variables
>   firmware: bcm47xx_nvram: add helper checking for NVRAM
>   firmware: bcm47xx_nvram: extract code copying NVRAM
>   firmware: bcm47xx_nvram: look for NVRAM with for instead of while
>   firmware: bcm47xx_nvram: inline code checking NVRAM size
> 
>  drivers/firmware/broadcom/bcm47xx_nvram.c | 92 ++++++++++++-----------
>  1 file changed, 47 insertions(+), 45 deletions(-)

series applied to mips-next.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ