From: David Ahern <dsahern@gmail.com>
To: Doug Ledford <dledford@redhat.com>,
Steve Wise <swise@opengridcomputing.com>,
leon@kernel.org
Cc: stephen@networkplumber.org, netdev@vger.kernel.org,
linux-rdma@vger.kernel.org
Subject: Re: [PATCH v2 iproute2-next 1/3] rdma: update rdma_netlink.h to get new driver attributes
Date: Tue, 15 May 2018 14:01:51 -0600 [thread overview]
Message-ID: <fd64ce39-a284-b09f-85b0-8cd7ba0d1207@gmail.com> (raw)
In-Reply-To: <d4a8a280c94dd8db969bc52abe057af1fde89a4b.camel@redhat.com>
On 5/15/18 2:00 PM, Doug Ledford wrote:
> I just sent an incremental fix to the list under separate cover. You
> can squash that fix into Steve's patch and it should resolve the issue.
> Or Steve can respin the set. Either way.
Once the patch has been committed to the upstream repo, spin a new set
with the correct header update.
next prev parent reply other threads:[~2018-05-15 20:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 15:43 [PATCH v2 iproute2-next 0/3] RDMA tool driver-specific resource tracking Steve Wise
2018-05-14 15:42 ` [PATCH v2 iproute2-next 1/3] rdma: update rdma_netlink.h to get new driver attributes Steve Wise
2018-05-15 19:37 ` David Ahern
2018-05-15 19:47 ` Doug Ledford
2018-05-15 19:53 ` David Ahern
2018-05-15 20:00 ` Doug Ledford
2018-05-15 20:01 ` David Ahern [this message]
2018-05-15 20:05 ` Doug Ledford
2018-05-15 20:29 ` Steve Wise
2018-05-15 20:29 ` Steve Wise
2018-05-15 20:25 ` Steve Wise
2018-05-15 20:25 ` Steve Wise
2018-05-15 19:52 ` Doug Ledford
2018-05-15 20:28 ` Steve Wise
2018-05-15 20:28 ` Steve Wise
2018-05-15 20:39 ` Doug Ledford
2018-05-14 15:42 ` [PATCH v2 iproute2-next 2/3] rdma: print driver resource attributes Steve Wise
2018-05-14 15:42 ` [PATCH v2 iproute2-next 3/3] rdma: update man pages Steve Wise
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=fd64ce39-a284-b09f-85b0-8cd7ba0d1207@gmail.com \
--to=dsahern@gmail.com \
--cc=dledford@redhat.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=swise@opengridcomputing.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.