netdev - Re: [PATCH v2] mlxsw: convert to pci_alloc_irq

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: <20170407.071405.627036901988213530.davem@davemloft.net>
Date:   Fri, 07 Apr 2017 07:14:05 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     idosch@...sch.org
Cc:     hch@....de, jiri@...lanox.com, idosch@...lanox.com,
        netdev@...r.kernel.org
Subject: Re: [PATCH v2] mlxsw: convert to pci_alloc_irq_vectors

From: Ido Schimmel <idosch@...sch.org>
Date: Fri, 7 Apr 2017 16:08:08 +0300

> Hi Dave,
> 
> On Thu, Apr 06, 2017 at 03:43:20PM +0300, Ido Schimmel wrote:
>> On Thu, Apr 06, 2017 at 02:23:03PM +0200, Christoph Hellwig wrote:
>> > Trivial conversion as only one vector is supported, but at least we
>> > lose the useless msix_entry member in the per-device structure.
>> > 
>> > Signed-off-by: Christoph Hellwig <hch@....de>
>> 
>> For net-next:
> 
> I noticed this is marked as "Not Applicable" in patchwork:
> https://patchwork.ozlabs.org/patch/747723/
> 
> But I'm not quite sure why. Maybe you meant to mark only v1?
> https://patchwork.ozlabs.org/patch/747674/

If the last patch of his series removes a kernel global API,
it shouldn't go via my tree.  He can send it directly to Linus
or via the PCI maintainer.