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:   Tue, 25 Feb 2020 07:23:50 +0100
From:   Heiner Kallweit <hkallweit1@...il.com>
To:     David Miller <davem@...emloft.net>
Cc:     bhelgaas@...gle.com, nic_swsd@...ltek.com, mlindner@...vell.com,
        stephen@...workplumber.org, clemens@...isch.de, perex@...ex.cz,
        tiwai@...e.com, linux-pci@...r.kernel.org,
        linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
        alsa-devel@...a-project.org
Subject: Re: [PATCH 0/9] PCI: add and use constant PCI_STATUS_ERROR_BITS and
 helper pci_status_get_and_clear_errors

On 25.02.2020 00:33, David Miller wrote:
> From: Heiner Kallweit <hkallweit1@...il.com>
> Date: Mon, 24 Feb 2020 22:20:08 +0100
> 
>> Few drivers have own definitions for this constant, so move it to the
>> PCI core. In addition there are several places where the following
>> code sequence is used:
>> 1. Read PCI_STATUS
>> 2. Mask out non-error bits
>> 3. Action based on set error bits
>> 4. Write back set error bits to clear them
>>
>> As this is a repeated pattern, add a helper to the PCI core.
>>
>> Most affected drivers are network drivers. But as it's about core
>> PCI functionality, I suppose the series should go through the PCI
>> tree.
> 
> Heiner, something is up with this submission.
> 
> The subject line here says 0/9, but the patches say N/8 and patch #8 never
> showed up on the list.
> 
> Sort out what this should be and resubmit, thank you.
> 
Oops, sorry. I'll resubmit.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ