From: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Dennis Dalessandro
<dennis.dalessandro-ral2JQCrhuEAvxtiuMwx3w@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: Thu, 27 Jul 2017 19:23:23 -0400 [thread overview]
Message-ID: <1501197803.2593.10.camel@redhat.com> (raw)
In-Reply-To: <7aad42cd-05be-b7a7-9e85-2c13f5d489d3-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
On Thu, 2017-07-27 at 14:32 -0400, Doug Ledford wrote:
> On 7/26/2017 9:03 AM, Leon Romanovsky wrote:
> > On Wed, Jul 26, 2017 at 08:24:44AM -0400, Dennis Dalessandro wrote:
> > > 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.
> >
> > Are you referring to this branch?
> > https://github.com/torvalds/linux/compare/master...dledford:k.o/for
> > -next
> >
> > It doesn't have most of mlx5/mlx4/cavium/core/e.t.c features.
>
> I created a for-next and then I've been making various other branches
> through the week and sending them to github to be checked by 0day
> testing. Once they pass 0day, I merge them into the for-next and
> push
> one more time to make sure the combination of everything merged
> together
> passes 0day, and once I get confirmation that the build is good, I'll
> push it to k.o where it will be considered unrebaseable, and so any
> fixes after that may require incremental patches, reverts, etc. The
> slowdown this week has largely been the turnaround time on 0day
> testing.
> That's been taking in excess of 10 hours from a push to test results
> :-/. I pushed what I want to push to k.o this morning about 8am, not
> sure when I'll get my 0day results back.
The current for-next is pushed to k.o.
--
Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
GPG KeyID: B826A3330E572FDD
Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
--
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
next prev parent reply other threads:[~2017-07-27 23:23 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
[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 [this message]
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=1501197803.2593.10.camel@redhat.com \
--to=dledford-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=dennis.dalessandro-ral2JQCrhuEAvxtiuMwx3w@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