From: Sowmini Varadhan <sowmini.varadhan@oracle•com>
To: David Miller <davem@davemloft•net>
Cc: ecree@solarflare•com, linux-net-drivers@solarflare•com,
netdev@vger•kernel.org, linville@tuxdriver•com
Subject: Re: [PATCH net-next 0/2] ntuple filters with RSS
Date: Tue, 27 Feb 2018 12:48:24 -0500 [thread overview]
Message-ID: <20180227174824.GA29950@oracle.com> (raw)
In-Reply-To: <20180227.124012.1918233209827542671.davem@davemloft.net>
On (02/27/18 12:40), David Miller wrote:
>
> I'm expecting a V3 respin of your zerocopy notification changes
> if that is what you're talking about, and I therefore marked
> the most recent spin as "changes requested".
sorry, I'm confused - you are waiting for V4?
I am not seeing v3 on patchwork, the only thing I see
is V2 (with "changes requested" as I expected).
V3 is archived here, and afaik needs no more respins:
https://www.spinics.net/lists/netdev/msg485282.html
Willem had responded with
" For the series:
Acked-by Willem de Bruijn <willemb@google•com>
Small item I missed in v2: the recvmsg in patch 3 should fail hard with
error() on an unexpected errno. Not worth sending a v4 just for that."
(see https://www.spinics.net/lists/netdev/msg485418.html)
Santosh had incorrectly flagged a smatch non-issue:
https://www.spinics.net/lists/netdev/msg485424.html
I resent my patch a few minutes ago, but I suspect I may
now be hitting this well-known patchwork bug:
https://www.spinics.net/lists/sparclinux/msg13787.html
Do I need to do something?
--Sowmini
next prev parent reply other threads:[~2018-02-27 17:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a9ac4273-e8b9-e0dd-a067-2b74bc1f9615@solarflare.com>
2018-02-27 16:39 ` [PATCH net-next 0/2] ntuple filters with RSS David Miller
[not found] ` <edd1c1ea-8c53-5900-9ed0-3f4ed11249b4@solarflare.com>
2018-02-27 16:49 ` David Miller
2018-02-27 16:51 ` Sowmini Varadhan
2018-02-27 17:40 ` David Miller
2018-02-27 17:48 ` Sowmini Varadhan [this message]
2018-02-27 18:00 ` David Miller
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=20180227174824.GA29950@oracle.com \
--to=sowmini.varadhan@oracle$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=ecree@solarflare$(echo .)com \
--cc=linux-net-drivers@solarflare$(echo .)com \
--cc=linville@tuxdriver$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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