From: Sowmini Varadhan <sowmini.varadhan@oracle.com>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, rds-devel@oss.oracle.com,
sowmini.varadhan@oracle.com, santosh.shilimkar@oracle.com
Subject: [PATCH net-next 0/2] RDS: TCP: bug fixes
Date: Fri, 4 Nov 2016 10:04:10 -0700 [thread overview]
Message-ID: <cover.1478276221.git.sowmini.varadhan@oracle.com> (raw)
A couple of bug fixes identified during testing.
Sowmini Varadhan (2):
RDS: TCP: report addr/port info based on TCP socket in rds-info
RDS: TCP: start multipath acceptor loop at 0
net/rds/tcp.c | 20 +++++++++++++-------
net/rds/tcp_listen.c | 2 +-
2 files changed, 14 insertions(+), 8 deletions(-)
next reply other threads:[~2016-11-04 17:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-04 17:04 Sowmini Varadhan [this message]
2016-11-04 17:04 ` [PATCH net-next 1/2] RDS: TCP: report addr/port info based on TCP socket in rds-info Sowmini Varadhan
2016-11-04 17:04 ` [PATCH net-next 2/2] RDS: TCP: start multipath acceptor loop at 0 Sowmini Varadhan
2016-11-09 17:48 ` [PATCH net-next 0/2] RDS: TCP: bug fixes 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=cover.1478276221.git.sowmini.varadhan@oracle.com \
--to=sowmini.varadhan@oracle.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=rds-devel@oss.oracle.com \
--cc=santosh.shilimkar@oracle.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).