public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Dennis Dalessandro <dennis.dalessandro-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Jason Gunthorpe
	<jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
Subject: Re: Latest for-4.14
Date: Wed, 26 Jul 2017 08:24:44 -0400	[thread overview]
Message-ID: <b337a2ae-40ff-a207-82fa-fd3c7d2e1083@intel.com> (raw)
In-Reply-To: <20170726053749.GV3259-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>

On 7/26/2017 1:37 AM, Leon Romanovsky wrote:
> Reply to: "Re: [PATCH for-next 7/9] IB/core: Allow QP state transition from reset to error"
> 
> On Sun, Jul 23, 2017 at 09:14:02AM -0400, Doug Ledford wrote:
>> On 7/23/2017 9:04 AM, Leon Romanovsky wrote:
> 
> <snip>
> 
>>> BTW, when will you post for-4.14 branch so we will be able to base our
>>> submission queue for the -next?
>>
>> Tomorrow.  I wanted to base it on 4.13-rc2 so it would get all of the
>> fixes that went in this week.
> 
> Any news on the matter?
> 

Check Doug's GitHub, I see a 4.13-rc2 based "for-next" branch there.

-Denny

--
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:[~2017-07-26 12:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-26  5:37 Latest for-4.14 Leon Romanovsky
     [not found] ` <20170726053749.GV3259-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-07-26 12:24   ` Dennis Dalessandro [this message]
     [not found]     ` <b337a2ae-40ff-a207-82fa-fd3c7d2e1083-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2017-07-26 13:03       ` Leon Romanovsky
     [not found]         ` <20170726130350.GW3259-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-07-27 18:32           ` Doug Ledford
     [not found]             ` <7aad42cd-05be-b7a7-9e85-2c13f5d489d3-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-07-27 23:23               ` Doug Ledford
2017-07-27 18:34           ` Doug Ledford
     [not found]             ` <a1abee42-58d2-aba6-bc56-9bf1830a4539-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-07-28  4:32               ` Leon Romanovsky
     [not found]                 ` <20170728043233.GE13672-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-07-28 16:54                   ` Doug Ledford
     [not found]                     ` <1501260896.2593.18.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-07-28 19:29                       ` Leon Romanovsky
     [not found]                         ` <20170728192930.GH13672-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-07-28 19:42                           ` Doug Ledford
     [not found]                             ` <347f8b97-6b81-94a7-d71b-7023d2ed3dac-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-07-29  9:23                               ` 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=b337a2ae-40ff-a207-82fa-fd3c7d2e1083@intel.com \
    --to=dennis.dalessandro-ral2jqcrhueavxtiumwx3w@public.gmane.org \
    --cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org \
    --cc=leon-DgEjT+Ai2ygdnm+yROfE0A@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