netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: idosch@idosch.org
Cc: hch@lst.de, jiri@mellanox.com, idosch@mellanox.com,
	netdev@vger.kernel.org
Subject: Re: [PATCH v2] mlxsw: convert to pci_alloc_irq_vectors
Date: Fri, 07 Apr 2017 07:14:05 -0700 (PDT)	[thread overview]
Message-ID: <20170407.071405.627036901988213530.davem@davemloft.net> (raw)
In-Reply-To: <20170407130808.GA31087@splinter>

From: Ido Schimmel <idosch@idosch.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@lst.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.

  reply	other threads:[~2017-04-07 14:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-06 12:23 [PATCH v2] mlxsw: convert to pci_alloc_irq_vectors Christoph Hellwig
2017-04-06 12:43 ` Ido Schimmel
2017-04-07 13:08   ` Ido Schimmel
2017-04-07 14:14     ` David Miller [this message]
2017-04-10  7:35       ` Christoph Hellwig
2017-04-10 14:06         ` David Miller
2017-04-10 14:37           ` Christoph Hellwig
2017-04-06 12:59 ` Jiri Pirko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170407.071405.627036901988213530.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=hch@lst.de \
    --cc=idosch@idosch.org \
    --cc=idosch@mellanox.com \
    --cc=jiri@mellanox.com \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).