From: David Miller <davem@davemloft.net>
To: hch@lst.de
Cc: idosch@idosch.org, jiri@mellanox.com, idosch@mellanox.com,
netdev@vger.kernel.org
Subject: Re: [PATCH v2] mlxsw: convert to pci_alloc_irq_vectors
Date: Mon, 10 Apr 2017 07:06:16 -0700 (PDT) [thread overview]
Message-ID: <20170410.070616.478356283361143853.davem@davemloft.net> (raw)
In-Reply-To: <20170410073551.GA6036@lst.de>
From: Christoph Hellwig <hch@lst.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!
next prev parent reply other threads:[~2017-04-10 14:06 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
2017-04-10 7:35 ` Christoph Hellwig
2017-04-10 14:06 ` David Miller [this message]
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=20170410.070616.478356283361143853.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).