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

From: Christoph Hellwig <hch@....de>
Date: Mon, 10 Apr 2017 09:35:51 +0200

> On Fri, Apr 07, 2017 at 07:14:05AM -0700, David Miller wrote:
>> >> 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.
> 
> This is a single patch that does not remove anything.
> 
> For the different series I explicitly asked if it's okay if the whole
> thing goes in through the net tree and Bjorn was fine it.  If you're
> not it would be nice if you could state that in the series so that
> the submitter can act on it.

My bad I thought this was part of that series.

Could you do me a favor and repost that series, with this mlxsw
patch added to it.  I will apply it to net-next.

Thanks!