Message ID | 20181210190948.6892-1-kamalheib1@gmail.com (mailing list archive) |
---|---|
Headers | show |
Series | RDMA: Add support for ib_device_ops | expand |
On Mon, Dec 10, 2018 at 09:09:28PM +0200, Kamal Heib wrote: > This patchset introduce a new structure that will contain all the > infiniband device operations, the structure will be used by the > providers to initialize their supported operations. This patchset also > includes the required changes in the core and ulps to start using it. > > Changes from v4: > * Include the missing fist patch. > * Include patch [1] that this patch set depend on and it should be > dropped when merging for-rc with for-next. This isn't a merge, you just included the commit, this makes patchworks confusing, try not to do it again, no need to resend. Jason
On 12/10/2018 1:26 PM, Jason Gunthorpe wrote: > On Mon, Dec 10, 2018 at 09:09:28PM +0200, Kamal Heib wrote: >> This patchset introduce a new structure that will contain all the >> infiniband device operations, the structure will be used by the >> providers to initialize their supported operations. This patchset also >> includes the required changes in the core and ulps to start using it. >> >> Changes from v4: >> * Include the missing fist patch. >> * Include patch [1] that this patch set depend on and it should be >> dropped when merging for-rc with for-next. > This isn't a merge, you just included the commit, this makes > patchworks confusing, try not to do it again, no need to resend. > > Jason Hey Jason, does this mean I should not include Yuval's patch [1] as part of my next newlink/dellink submission? [1] https://www.spinics.net/lists/linux-rdma/msg71957.html Thanks, Steve.
On Mon, Dec 10, 2018 at 01:45:01PM -0600, Steve Wise wrote: > > On 12/10/2018 1:26 PM, Jason Gunthorpe wrote: > > On Mon, Dec 10, 2018 at 09:09:28PM +0200, Kamal Heib wrote: > >> This patchset introduce a new structure that will contain all the > >> infiniband device operations, the structure will be used by the > >> providers to initialize their supported operations. This patchset also > >> includes the required changes in the core and ulps to start using it. > >> > >> Changes from v4: > >> * Include the missing fist patch. > >> * Include patch [1] that this patch set depend on and it should be > >> dropped when merging for-rc with for-next. > > This isn't a merge, you just included the commit, this makes > > patchworks confusing, try not to do it again, no need to resend. > > > > Jason > > Hey Jason, does this mean I should not include Yuval's patch [1] as part > of my next newlink/dellink submission? > > [1] https://www.spinics.net/lists/linux-rdma/msg71957.html It hasn't been merged so you are kind of stuck to resend it.. But it had comments so it needed respin Jason
On Mon, Dec 10, 2018 at 01:05:43PM -0700, Jason Gunthorpe wrote: > On Mon, Dec 10, 2018 at 01:45:01PM -0600, Steve Wise wrote: > > > > On 12/10/2018 1:26 PM, Jason Gunthorpe wrote: > > > On Mon, Dec 10, 2018 at 09:09:28PM +0200, Kamal Heib wrote: > > >> This patchset introduce a new structure that will contain all the > > >> infiniband device operations, the structure will be used by the > > >> providers to initialize their supported operations. This patchset also > > >> includes the required changes in the core and ulps to start using it. > > >> > > >> Changes from v4: > > >> * Include the missing fist patch. > > >> * Include patch [1] that this patch set depend on and it should be > > >> dropped when merging for-rc with for-next. > > > This isn't a merge, you just included the commit, this makes > > > patchworks confusing, try not to do it again, no need to resend. > > > > > > Jason > > > > Hey Jason, does this mean I should not include Yuval's patch [1] as part > > of my next newlink/dellink submission? > > > > [1] https://www.spinics.net/lists/linux-rdma/msg71957.html > > It hasn't been merged so you are kind of stuck to resend it.. > > But it had comments so it needed respin The sole comment (inlining rxe_set_port_state) was addressed. > > Jason
On Mon, Dec 10, 2018 at 09:09:28PM +0200, Kamal Heib wrote: > This patchset introduce a new structure that will contain all the > infiniband device operations, the structure will be used by the > providers to initialize their supported operations. This patchset also > includes the required changes in the core and ulps to start using it. I'm inclined to apply this, do people still have concerns to the approach in this v5 version? Jason
On Tue, Dec 11, 2018 at 05:42:30PM +0000, Jason Gunthorpe wrote: > On Mon, Dec 10, 2018 at 09:09:28PM +0200, Kamal Heib wrote: > > This patchset introduce a new structure that will contain all the > > infiniband device operations, the structure will be used by the > > providers to initialize their supported operations. This patchset also > > includes the required changes in the core and ulps to start using it. > > I'm inclined to apply this, do people still have concerns to the > approach in this v5 version? > > Jason I'm not sure if you saw my reply to Yuval..., in the commit message of the first patch need to replace "ib_device_ops()" with "ib_set_device_ops()". Please let me know if you think that I need to re-send the patch with a fixed commit message. Thanks, Kamal
On Tue, 2018-12-11 at 17:42 +0000, Jason Gunthorpe wrote: > On Mon, Dec 10, 2018 at 09:09:28PM +0200, Kamal Heib wrote: > > This patchset introduce a new structure that will contain all the > > infiniband device operations, the structure will be used by the > > providers to initialize their supported operations. This patchset also > > includes the required changes in the core and ulps to start using it. > > I'm inclined to apply this, do people still have concerns to the > approach in this v5 version? > > Jason I'm OK with merging it.
On Tue, Dec 11, 2018 at 01:18:47PM -0500, Doug Ledford wrote: > On Tue, 2018-12-11 at 17:42 +0000, Jason Gunthorpe wrote: > > On Mon, Dec 10, 2018 at 09:09:28PM +0200, Kamal Heib wrote: > > > This patchset introduce a new structure that will contain all the > > > infiniband device operations, the structure will be used by the > > > providers to initialize their supported operations. This patchset also > > > includes the required changes in the core and ulps to start using it. > > > > I'm inclined to apply this, do people still have concerns to the > > approach in this v5 version? > > > > Jason > > I'm OK with merging it. +1 on that. > > -- > Doug Ledford <dledford@redhat.com> > GPG KeyID: B826A3330E572FDD > Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
On Mon, Dec 10, 2018 at 09:09:28PM +0200, Kamal Heib wrote: > This patchset introduce a new structure that will contain all the > infiniband device operations, the structure will be used by the > providers to initialize their supported operations. This patchset also > includes the required changes in the core and ulps to start using it. > > Changes from v4: > * Include the missing fist patch. > * Include patch [1] that this patch set depend on and it should be > dropped when merging for-rc with for-next. > > [1] RDMA/rdmavt: Fix rvt_create_ah function signature So, I almost didn't apply this, particularly since I don't see how it could have even worked with that ops bug, and it didn't apply cleanly.. But I fixed all the merge issues and fixed the bug, and the pointless checkpatch violations. So applied to for-next You should probably check carefully. Maybe run some tests... Jason
On 12/12/18 1:01 AM, Jason Gunthorpe wrote: > On Mon, Dec 10, 2018 at 09:09:28PM +0200, Kamal Heib wrote: >> This patchset introduce a new structure that will contain all the >> infiniband device operations, the structure will be used by the >> providers to initialize their supported operations. This patchset also >> includes the required changes in the core and ulps to start using it. >> >> Changes from v4: >> * Include the missing fist patch. >> * Include patch [1] that this patch set depend on and it should be >> dropped when merging for-rc with for-next. >> >> [1] RDMA/rdmavt: Fix rvt_create_ah function signature > > So, I almost didn't apply this, particularly since I don't see how it > could have even worked with that ops bug, and it didn't apply > cleanly.. But I fixed all the merge issues and fixed the bug, and the > pointless checkpatch violations. So applied to for-next > > You should probably check carefully. Maybe run some tests... > > Jason > Hi Jason, We have two issues that got fixed: 1- when CONFIG_MLX5_CORE_IPOIB isn't set: I already sent a fixup off the list that should fix it, but I also saw that Leaon sent it too. 2- Reading the ibdev_fn. So, I tested "rdma/wip/jgg-for-next" with the above two fixes on top of it and it looks good to me. Thanks, Kamal