From: David Miller <davem@davemloft.net>
To: gerd.rausch@oracle.com
Cc: santosh.shilimkar@oracle.com, netdev@vger.kernel.org,
linux-rdma@vger.kernel.org, rds-devel@oss.oracle.com
Subject: Re: [PATCH net-next v2 0/4] net/rds: Fixes from internal Oracle repo
Date: Thu, 15 Aug 2019 12:04:37 -0700 (PDT) [thread overview]
Message-ID: <20190815.120437.1520245379792336202.davem@davemloft.net> (raw)
In-Reply-To: <ee77e550-2231-be7f-861f-31d609631e9f@oracle.com>
From: Gerd Rausch <gerd.rausch@oracle.com>
Date: Thu, 15 Aug 2019 07:40:22 -0700
> This is the first set of (mostly old) patches from our internal repository
> in an effort to synchronize what Oracle had been using internally
> with what is shipped with the Linux kernel.
Series applied.
next prev parent reply other threads:[~2019-08-15 19:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-13 18:20 [PATCH net-next 1/5] RDS: Re-add pf/sol access via sysctl Gerd Rausch
2019-08-13 22:07 ` santosh.shilimkar
2019-08-14 15:56 ` Doug Ledford
2019-08-14 17:41 ` Gerd Rausch
2019-08-14 18:01 ` santosh.shilimkar
2019-08-14 18:21 ` David Miller
2019-08-14 18:36 ` santosh.shilimkar
2019-08-14 21:31 ` David Miller
2019-08-14 21:45 ` Gerd Rausch
2019-08-15 1:25 ` David Miller
2019-08-15 14:40 ` [PATCH net-next v2 0/4] net/rds: Fixes from internal Oracle repo Gerd Rausch
2019-08-15 19:04 ` David Miller [this message]
[not found] ` <cover.1565879451.git.gerd.rausch@oracle.com>
2019-08-15 14:42 ` [PATCH net-next v2 1/4] RDS: limit the number of times we loop in rds_send_xmit Gerd Rausch
2019-08-15 16:16 ` santosh.shilimkar
2019-08-15 14:42 ` [PATCH net-next v2 2/4] RDS: don't use GFP_ATOMIC for sk_alloc in rds_create Gerd Rausch
2019-08-15 16:17 ` santosh.shilimkar
2019-08-15 14:42 ` [PATCH net-next v2 3/4] net/rds: Add a few missing rds_stat_names entries Gerd Rausch
2019-08-15 16:17 ` santosh.shilimkar
2019-08-15 14:43 ` [PATCH net-next v2 4/4] rds: check for excessive looping in rds_send_xmit Gerd Rausch
2019-08-15 16:18 ` santosh.shilimkar
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=20190815.120437.1520245379792336202.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=gerd.rausch@oracle.com \
--cc=linux-rdma@vger.kernel.org \
--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