public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: RDMA mailing list <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Prepared RDMA Tree for 4.7
Date: Sat, 14 May 2016 07:33:53 +0300	[thread overview]
Message-ID: <20160514043353.GG11827@leon.nu> (raw)
In-Reply-To: <9e5233c8-6641-7f6b-3825-1b67eb70c05b-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 678 bytes --]

On Fri, May 13, 2016 at 12:31:55PM -0400, Doug Ledford wrote:

<snip>

I had an intent to help you, since there was kernel oops fix
which wasn't applied for more than month [1] and Christoph/Bart/Steve
asked your plans about important ULP API change [2], which you
decided do not announce.

We all agree that applying patches is not the time
consuming process and you can handle it by yourself.

So can you please share with us your plans on how-to address the
general lack of "communication, transparency and coordination",
which is definitely happen here?

[1] http://permalink.gmane.org/gmane.linux.drivers.rdma/35409
[2] http://marc.info/?l=linux-rdma&m=146229128832706&w=2

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  parent reply	other threads:[~2016-05-14  4:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-12 17:44 Prepared RDMA Tree for 4.7 Leon Romanovsky
     [not found] ` <20160512174406.GB11827-2ukJVAZIZ/Y@public.gmane.org>
2016-05-12 17:47   ` Leon Romanovsky
2016-05-13  2:01   ` Doug Ledford
     [not found]     ` <9dbc023f-e442-843a-ab68-eec38ca1d6b7-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-05-13  4:22       ` Leon Romanovsky
     [not found]         ` <20160513042217.GD11827-2ukJVAZIZ/Y@public.gmane.org>
2016-05-13 16:31           ` Doug Ledford
     [not found]             ` <9e5233c8-6641-7f6b-3825-1b67eb70c05b-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-05-14  4:33               ` Leon Romanovsky [this message]
     [not found]                 ` <20160514043353.GG11827-2ukJVAZIZ/Y@public.gmane.org>
2016-05-14 13:09                   ` Doug Ledford
     [not found]                     ` <f9210e1d-667d-5f62-f1bd-7545a0ff6153-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-05-15  6:00                       ` Leon Romanovsky
     [not found]                         ` <20160515060005.GH11827-2ukJVAZIZ/Y@public.gmane.org>
2016-05-16 20:15                           ` Doug Ledford
     [not found]                             ` <04c7b983-66b4-0609-9cf4-3c7b1e126a53-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-05-17 13:38                               ` Leon Romanovsky
2016-05-18 13:18                             ` Daniel Jurgens

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=20160514043353.GG11827@leon.nu \
    --to=leon-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
    --cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.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