From: Benjamin Poirier <benjamin.poirier@gmail.com>
To: Ursula Braun <ubraun@linux.vnet.ibm.com>
Cc: Dave Miller <davem@davemloft.net>,
netdev@vger.kernel.org, linux-s390@vger.kernel.org,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Utz Bacher <utz.bacher@de.ibm.com>
Subject: Re: Fwd: Fwd: Re: [PATCH net-next 00/15] net/smc: Shared Memory Communications - RDMA
Date: Tue, 12 Jul 2016 11:10:36 -0700 [thread overview]
Message-ID: <20160712181036.lgh7d4bbxwf53sxz@f1.synalogic.ca> (raw)
In-Reply-To: <20160712180820.72hfh4ihzxjqvx5f@f1.synalogic.ca>
On 2016/07/12 11:08, Benjamin Poirier wrote:
> On 2016/07/06 17:29, Ursula Braun wrote:
> > Dave,
> >
> > we still like to see SMC-R included into a future Linux-kernel. After
> > answering your first 2 questions, there is no longer a response. What should
> > we do next?
> > - Still wait for an answer from you?
> > - Resend the same whole SMC-R patch series, this time with the cover letter
> > adapted to your requested changes?
>
> ^^^ I would suggest to send v2 of the patch series with the changes
> that were requested.
>
> > - Put the SMC-R development on hold, and concentrate on another
> > s390-specific SMC-solution first (not RDMA-based), that makes use of the
> > SMC-socket family as well.
> > - Anything else?
> >
... and I would suggest to trim my emails next time. Sorry.
prev parent reply other threads:[~2016-07-12 18:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201606031527.u53FQ9dR045418@mx0a-001b2d01.pphosted.com>
2016-06-06 22:17 ` [PATCH net-next 00/15] net/smc: Shared Memory Communications - RDMA David Miller
2016-06-07 22:07 ` David Miller
2016-06-09 15:36 ` Ursula Braun
2016-06-21 14:02 ` Fwd: " Ursula Braun
2016-07-06 15:29 ` Fwd: " Ursula Braun
2016-07-12 18:08 ` Benjamin Poirier
2016-07-12 18:10 ` Benjamin Poirier [this message]
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=20160712181036.lgh7d4bbxwf53sxz@f1.synalogic.ca \
--to=benjamin.poirier@gmail.com \
--cc=davem@davemloft.net \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
--cc=ubraun@linux.vnet.ibm.com \
--cc=utz.bacher@de.ibm.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).