On Mon, 2018-12-03 at 10:44 -0700, Jason Gunthorpe wrote:
> On Mon, Dec 03, 2018 at 12:42:26PM -0500, Doug Ledford wrote:
> > > That is the right branch, but there are three series reworking write,
> > > only the first two are applied, the last one still in patchworks
> > > didn't get applied yet..
> >
> > Ahh, see, the cover page for this series states:
> >
> > Based on "Have the core handler dispatch code create the driver udata"
> > series:
>
> Yes, that one is done now..
>
> > And I saw that series was applied. No big deal, nothing pushed, so I'll
> > leave this in its current branch. The final one needed is this one then
> > (a single patch, not a series), yes?
>
> And this is where I got mixed up..
>
> > [rdma-next] RDMA/uverbs: Implement an ioctl that can call write and
> > write_ex handlers
> >
> > > And this patch has to go after the prior three for all the bits to
> > > work properly, and as a uapi change it should ideally wait for the
> > > corresponding rdma-core patch to be posted..
> >
> > Fair enough. Is that coming soon?
>
> And this remark was refering to the above patch not this one. :(
>
> The write() series is fine, I was going to apply it on Friday but
> didn't have time.
Ok, makes sense. So, with all that straightened out, this series is
applied. I forced a merge commit to be able to capture the cover letter
too.
--
Doug Ledford <dledford@xxxxxxxxxx>
GPG KeyID: B826A3330E572FDD
Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
Attachment:
signature.asc
Description: This is a digitally signed message part
