FYI, the only conflict as reported in linux-next last week is with nfsd
tree and "IB: merge struct ib_device_attr into struct ib_device" here:
http://marc.info/?l=linux-next=145155049101826=2
It looks like there is ongoing discussion this morning wrt rdma + nfsd
trees..
Do you still want
On Thu, 2015-12-24 at 12:22 +0200, Sagi Grimberg wrote:
> >> Applied to target-pending/for-next as v4.5-rc1 material, along with
> >> Reviewed-by tags from HCH.
> >
> > So this is both in your and Dougs now it seems. Given the non-trivial
> > merge with the other RDMA updates I'd suggest to drop
On Wed, Dec 23, 2015 at 10:53 PM, Or Gerlitz wrote:
> On Mon, Dec 21, 2015 at 3:29 PM, Sagi Grimberg
> wrote:
>
>>> Sagi, are you going to spin an increment in the initiator version?
>
>> I don't know if it's worth a driver version update?
>
>
> Applied to target-pending/for-next as v4.5-rc1 material, along with
> Reviewed-by tags from HCH.
So this is both in your and Dougs now it seems. Given the non-trivial
merge with the other RDMA updates I'd suggest to drop it from the
target tree as Doug already sorted out the merge.
--
To
Applied to target-pending/for-next as v4.5-rc1 material, along with
Reviewed-by tags from HCH.
So this is both in your and Dougs now it seems. Given the non-trivial
merge with the other RDMA updates I'd suggest to drop it from the
target tree as Doug already sorted out the merge.
Yea, this
Hey Nic,
Applied to target-pending/for-next as v4.5-rc1 material, along with
Reviewed-by tags from HCH.
Thanks for picking this up!
Note that I expect this patchset will conflict with Doug's pull request
in case he's taking Christoph's device_attr and CQ abstraction patches
for 4.5.
Doug,
Sagi, are you going to spin an increment in the initiator version?
I don't know if it's worth a driver version update?
In case we do increment, I can send an incremental patch instead of
re-spinning the entire series.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma"
On Mon, Dec 21, 2015 at 6:20 AM, Nicholas A. Bellinger
wrote:
> Applied to target-pending/for-next as v4.5-rc1 material, along with
> Reviewed-by tags from HCH.
Hi Nic, thanks for stepping in and picking that.
Sagi, are you going to spin an increment in the initiator
Hi Sagi, Jenny & Co,
On Wed, 2015-12-09 at 14:11 +0200, Sagi Grimberg wrote:
> Changes from v1:
> - Fixed change-log typos
>
> Changes from v0:
> - Rebased on top of 4.4-rc2
> - Removed iser_hello messages from the protocol header
> - Avoided from further breaking the non-existent bidi support
>
Changes from v1:
- Fixed change-log typos
Changes from v0:
- Rebased on top of 4.4-rc2
- Removed iser_hello messages from the protocol header
- Avoided from further breaking the non-existent bidi support
- Fixed initiator remote invalidate support exposure only
for fastreg &&
10 matches
Mail list logo