From: Sowmini Varadhan <sowmini.varadhan@oracle.com>
To: Santosh Shilimkar <santosh.shilimkar@oracle.com>
Cc: netdev@vger.kernel.org, willemdebruijn.kernel@gmail.com,
davem@davemloft.net, Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [PATCH V3 net-next 2/3] rds: deliver zerocopy completion notification with data
Date: Mon, 26 Feb 2018 12:11:18 -0500 [thread overview]
Message-ID: <20180226171118.GC24804@oracle.com> (raw)
In-Reply-To: <950eb12c-0520-3656-6667-c13148cec326@oracle.com>
On (02/26/18 09:07), Santosh Shilimkar wrote:
> Just in case you haven't seen yet, Dan Carpenter reported skb deref
> warning on previous version of the patch. Not sure why it wasn't sent
> on netdev.
yes I saw it, but that was for the previous version of the patch
around code that delivers notifications on sk_error_queue.
This patch series removes the sk_error_queue support to the
smatch warning is not applicable after this patch.
on a different note, for some odd reason I'm not seeing this patch series
on the patch queue, though its showing up in the archives.
--Sowmini
next prev parent reply other threads:[~2018-02-26 17:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 17:08 [PATCH RESEND V3 net-next 0/3] RDS: optimized notification for zerocopy completion Sowmini Varadhan
2018-02-26 16:56 ` [PATCH " Willem de Bruijn
2018-02-27 17:08 ` [PATCH RESEND V3 net-next 1/3] selftests/net: revert the zerocopy Rx path for PF_RDS Sowmini Varadhan
2018-02-27 17:08 ` [PATCH RESEND V3 net-next 2/3] rds: deliver zerocopy completion notification with data Sowmini Varadhan
2018-02-26 17:07 ` [PATCH " Santosh Shilimkar
2018-02-26 17:11 ` Sowmini Varadhan [this message]
2018-02-26 17:13 ` David Miller
2018-02-26 17:15 ` Santosh Shilimkar
2018-02-27 17:08 ` [PATCH RESEND V3 net-next 3/3] selftests/net: reap zerocopy completions passed up as ancillary data Sowmini Varadhan
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=20180226171118.GC24804@oracle.com \
--to=sowmini.varadhan@oracle.com \
--cc=dan.carpenter@oracle.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=santosh.shilimkar@oracle.com \
--cc=willemdebruijn.kernel@gmail.com \
/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).