From: David Miller <davem@davemloft.net>
To: Yuval.Mintz@cavium.com
Cc: netdev@vger.kernel.org, Michal.Kalderon@cavium.com,
linux-rdma@vger.kernel.org
Subject: Re: [PATCH v4 net-next 0/7] qed*: RDMA and infrastructure for iWARP
Date: Tue, 20 Jun 2017 12:35:51 -0400 (EDT) [thread overview]
Message-ID: <20170620.123551.765657502957371421.davem@davemloft.net> (raw)
In-Reply-To: <20170620130006.307-1-Yuval.Mintz@cavium.com>
From: Yuval Mintz <Yuval.Mintz@cavium.com>
Date: Tue, 20 Jun 2017 15:59:59 +0300
> Please consider applying this series to `net-next'.
Series applied, thanks.
next prev parent reply other threads:[~2017-06-20 16:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-20 12:59 [PATCH v4 net-next 0/7] qed*: RDMA and infrastructure for iWARP Yuval Mintz
2017-06-20 13:00 ` [PATCH v4 net-next 2/7] qed: RoCE EDPM to honor PFC Yuval Mintz
2017-06-20 13:00 ` [PATCH v4 net-next 3/7] qed: Disable RoCE dpm when DCBx change occurs Yuval Mintz
[not found] ` <20170620130006.307-1-Yuval.Mintz-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org>
2017-06-20 13:00 ` [PATCH v4 net-next 1/7] qed: Chain support for external PBL Yuval Mintz
2017-06-20 13:00 ` [PATCH v4 net-next 4/7] qed*: qede_roce.[ch] -> qede_rdma.[ch] Yuval Mintz
2017-06-20 13:00 ` [PATCH v4 net-next 5/7] qed*: Set rdma generic functions prefix Yuval Mintz
2017-06-20 13:00 ` [PATCH v4 net-next 7/7] qed: SPQ async callback registration Yuval Mintz
2017-06-20 13:00 ` [PATCH v4 net-next 6/7] qed: Wait for resources before FUNC_CLOSE Yuval Mintz
2017-06-20 16:35 ` David Miller [this message]
[not found] ` <20170620.123551.765657502957371421.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2017-06-21 9:56 ` [PATCH v4 net-next 0/7] qed*: RDMA and infrastructure for iWARP Or Gerlitz
[not found] ` <CAJ3xEMjyHidoAV9_VPkTM9dPdaXRFt8LmpcV_5iEvYEB+ujSmA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-06-21 9:57 ` Or Gerlitz
2017-06-21 10:10 ` Leon Romanovsky
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=20170620.123551.765657502957371421.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Michal.Kalderon@cavium.com \
--cc=Yuval.Mintz@cavium.com \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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).