Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: Yann Droneaud <ydroneaud-RlY5vtjFyJ3QT0dZR+AlfA@public.gmane.org>
To: Or Gerlitz <ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Cc: Roland Dreier <roland-BHEL68pLQRGGvPXPguhicg@public.gmane.org>,
	Roland Dreier <roland-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Matan Barak <matanb-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Subject: Re: [PATCH] IB/core: temporarily disable create_flow/destroy_flow uverbs
Date: Thu, 10 Oct 2013 12:12:03 +0200	[thread overview]
Message-ID: <5e07fcdfc494de9f83b56336b5c1aefa@meuh.org> (raw)
In-Reply-To: <525673BB.7020900-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>

Hi,

Le 10.10.2013 11:30, Or Gerlitz a écrit :
> On 10/10/2013 12:10, Yann Droneaud wrote:
>> create_flow/destroy_flow uverbs are under review and should
>> be considered too experimental at this point.
>> 
>> To not expose to userspace such experimental feature,
>> the data structure and code is temporarily disabled for v3.12.
>> 
>> The feature will be enabled after proper cleanup for v3.13.
> 
> NAK
> 
> The patches were on the list from April and went through review of
> Sean, Jason, Roland, Shawn and others.
> 
> You started your review few months after the point in time we
> submitted them, and after they were accepted.
> 
> We were very happy **and**  responsive for your feedback -- Matan sent
> patch on Sep 22nd to fix few issues you pointed on.
> 

I'm also very happy and looking forward to continue working with you
so I'm very sorry to provide the reviews so late (back in April I became
father for the second time).

I'm also very sorry bring such patch now but I feel I won't be able to
find the needed time to do the patchset rework before the deadline.
I will try to do this before the end of the week (12th october) but no 
promise.

> If you have more point fixes, we're **before** rc5 and 2-3 patches
> that fix things can get it, Matan review your prev
> patchset which contained four patches and acked three of them.
> 
> So you now need to re-prepare a smaller patch set advocate for Roland
> to pick it up.
> 

I'm also afraid that the whole patchset with extended command + public 
API fix
would be too big for v3.12-rc5 ... v3.12.

Regards.

-- 
Yann Droneaud
OPTEYA

--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2013-10-10 10:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-10  9:10 [PATCH] IB/core: temporarily disable create_flow/destroy_flow uverbs Yann Droneaud
     [not found] ` <1381396255-13005-1-git-send-email-ydroneaud-RlY5vtjFyJ3QT0dZR+AlfA@public.gmane.org>
2013-10-10  9:30   ` Or Gerlitz
     [not found]     ` <525673BB.7020900-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-10-10 10:12       ` Yann Droneaud [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=5e07fcdfc494de9f83b56336b5c1aefa@meuh.org \
    --to=ydroneaud-rly5vtjfyj3qt0dzr+alfa@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=matanb-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
    --cc=ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
    --cc=roland-BHEL68pLQRGGvPXPguhicg@public.gmane.org \
    --cc=roland-DgEjT+Ai2ygdnm+yROfE0A@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