Re: Latest for-4.14

Leon Romanovsky
2017-07-28T04:32:33Z

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

On Thu, Jul 27, 2017 at 02:34:57PM -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.
>
> Oh, and I never said I would be *done* processing the for-next area all
> in one go. You said you wanted regular progress and updates, and the
> branch I have represents that. But regular progress does not mean take
> everything all at once. As I process more patchsets, more will be added.
>

Regular sharing of information is also part of regular progress.

As I said more than once, I'm fine with sequential work, I'm fine with
the fact that not all my code is accepted, I'm fine with scheduled
delays, but I'm not fine with silence.

Thanks

>
> --
> Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
> GPG Key ID: B826A3330E572FDD
> Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]