Re: Stepping down as maintainer (was Re: [PATCH for-next 0/9] mlx4 changes in virtual GID management)
On Wed, 2015-04-22 at 10:10 -0700, Roland Dreier wrote: > On Wed, Apr 22, 2015 at 7:43 AM, Doug Ledford wrote: > > New items since the last push: > > > > Jason's fix to the CMA for IPv4/IPv6 canonization > > Hariprasad's series to iw_cxgb4 > > Tatyana's and Steve's series for iWARP portmapper address resolution > > I just sent the previous batch, since it is late in the merge window > and I didn't want to send things immediately without giving > linux-next, 0-day builds etc a chance to catch problems. > > I will pick these up and send to Linus around Friday. > > - R. That works. Thanks! -- Doug Ledford GPG KeyID: 0E572FDD signature.asc Description: This is a digitally signed message part
Re: Stepping down as maintainer (was Re: [PATCH for-next 0/9] mlx4 changes in virtual GID management)
On Wed, Apr 22, 2015 at 7:43 AM, Doug Ledford wrote: > New items since the last push: > > Jason's fix to the CMA for IPv4/IPv6 canonization > Hariprasad's series to iw_cxgb4 > Tatyana's and Steve's series for iWARP portmapper address resolution I just sent the previous batch, since it is late in the merge window and I didn't want to send things immediately without giving linux-next, 0-day builds etc a chance to catch problems. I will pick these up and send to Linus around Friday. - R. -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Stepping down as maintainer (was Re: [PATCH for-next 0/9] mlx4 changes in virtual GID management)
On Thu, 2015-04-16 at 16:18 -0600, Jason Gunthorpe wrote: > On Thu, Apr 16, 2015 at 06:03:19PM -0400, Doug Ledford wrote: > > > AFAIK, capturing provided tags is considered best practice as a way to > > > recognize and retain contributors. > > > > Agreed. I'll double check them tomorrow. > > These are two I noticed from memory: > > http://permalink.gmane.org/gmane.linux.drivers.rdma/24423 > https://lkml.org/lkml/2015/4/15/9 > > Jason Those have been fixed, and a few additional items have been added to the overall set and pushed to my github. New items since the last push: Jason's fix to the CMA for IPv4/IPv6 canonization Hariprasad's series to iw_cxgb4 Tatyana's and Steve's series for iWARP portmapper address resolution git://github.com/dledford/linux.git for-4.1 -- Doug Ledford GPG KeyID: 0E572FDD signature.asc Description: This is a digitally signed message part
Re: Stepping down as maintainer (was Re: [PATCH for-next 0/9] mlx4 changes in virtual GID management)
On Fri, Apr 17, 2015 at 8:03 PM, Roland Dreier wrote: > On Fri, Apr 17, 2015 at 4:15 AM, Or Gerlitz wrote: >> Seems like Roland isn't around to carry the rdma pull request for 4.1 ... > > Why do you ignore my emails (I see no reply to > http://www.spinics.net/lists/linux-rdma/msg24194.html) and jump to > this conclusion? Sorry, I misread where things are, I was under the impression that all was in place and expected you to pull things after you made this post @ Wednesday http://www.spinics.net/lists/linux-rdma/msg24191.html, NM, we're on track. Thanks a lot for driving the bits for the 4.1 merge window. > I will send a pull request for what is in Doug's tree (and also in my tree). cool -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Stepping down as maintainer (was Re: [PATCH for-next 0/9] mlx4 changes in virtual GID management)
On Apr 11, 2015 12:28 PM, "Or Gerlitz" wrote: > If taking off the maintainer hat would get you some free/spare cycles, > maybe you could resume posting in the digitalvampire blog and/or > participate in the upstreamming of soft-RoCE driver? some folks here > are working on this, so if you're interested, let me know... Thank you very much for the direction. I'm OK figuring out what to do for myself though. -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Stepping down as maintainer (was Re: [PATCH for-next 0/9] mlx4 changes in virtual GID management)
On Fri, Apr 17, 2015 at 4:15 AM, Or Gerlitz wrote: > Seems like Roland isn't around to carry the rdma pull request for 4.1 ... Why do you ignore my emails (I see no reply to http://www.spinics.net/lists/linux-rdma/msg24194.html) and jump to this conclusion? I will send a pull request for what is in Doug's tree (and also in my tree). -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Stepping down as maintainer (was Re: [PATCH for-next 0/9] mlx4 changes in virtual GID management)
On Fri, Apr 17, 2015 at 1:03 AM, Doug Ledford wrote: > On Thu, 2015-04-16 at 15:37 -0600, Jason Gunthorpe wrote: >> On Fri, Apr 17, 2015 at 12:26:47AM +0300, Or Gerlitz wrote: >> > On Thu, Apr 16, 2015 at 11:13 PM, Jason Gunthorpe >> > wrote: >> > > On Wed, Apr 15, 2015 at 08:39:13AM -0400, Doug Ledford wrote: >> > > >> > >> Let’s take this as a starting point. If there are other patches >> > >> people think should make 4.1, please bring them to my attention and >> > >> I’ll add them for review and possible addition to the list. >> > >> >> > >> git://github.com/dledford/linux.git for-4.1 >> > > >> > > I noticed a few patches didn't get Reviewed-By's etc from the mailing >> > > list annotated.. >> > >> > Every patch need not have a Reviewed-By annotation, it's perfectly up >> > to the maintainer judgement to make sure there was either consensus, >> >> More clearly: There were several patches where a Reviewed-By/etc was >> *provided* on-list but did not get captured in the git commit. > > Sure, that's what I figured you meant. That most likely means that I > pulled the bundle from patchworks before their review was captured. It > means I would need to either re-pull the bundle or manually add the > review. > >> AFAIK, capturing provided tags is considered best practice as a way to >> recognize and retain contributors. > > Agreed. I'll double check them tomorrow. Doug, Seems like Roland isn't around to carry the rdma pull request for 4.1 ... I assume the most safe way to do that would be ask Dave Miller to pull the patches from your tree into net-next ASAP, next, have them sit there for 1-2 days to pass linux-next etc auto merge tests, and then have Dave to send a pull request. Dave, I hope it would be OK from you to help us here with the 4.1-rc1 bits. For 4.2 and 4.1-rc > 1 Doug will should be ready for sending pull request directly to Linus. Or. -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Stepping down as maintainer (was Re: [PATCH for-next 0/9] mlx4 changes in virtual GID management)
On Thu, 2015-04-16 at 15:37 -0600, Jason Gunthorpe wrote: > On Fri, Apr 17, 2015 at 12:26:47AM +0300, Or Gerlitz wrote: > > On Thu, Apr 16, 2015 at 11:13 PM, Jason Gunthorpe > > wrote: > > > On Wed, Apr 15, 2015 at 08:39:13AM -0400, Doug Ledford wrote: > > > > > >> Let’s take this as a starting point. If there are other patches > > >> people think should make 4.1, please bring them to my attention and > > >> I’ll add them for review and possible addition to the list. > > >> > > >> git://github.com/dledford/linux.git for-4.1 > > > > > > I noticed a few patches didn't get Reviewed-By's etc from the mailing > > > list annotated.. > > > > Every patch need not have a Reviewed-By annotation, it's perfectly up > > to the maintainer judgement to make sure there was either consensus, > > More clearly: There were several patches where a Reviewed-By/etc was > *provided* on-list but did not get captured in the git commit. Sure, that's what I figured you meant. That most likely means that I pulled the bundle from patchworks before their review was captured. It means I would need to either re-pull the bundle or manually add the review. > AFAIK, capturing provided tags is considered best practice as a way to > recognize and retain contributors. Agreed. I'll double check them tomorrow. -- Doug Ledford GPG KeyID: 0E572FDD signature.asc Description: This is a digitally signed message part
Re: Stepping down as maintainer (was Re: [PATCH for-next 0/9] mlx4 changes in virtual GID management)
On Fri, Apr 17, 2015 at 12:26:47AM +0300, Or Gerlitz wrote: > On Thu, Apr 16, 2015 at 11:13 PM, Jason Gunthorpe > wrote: > > On Wed, Apr 15, 2015 at 08:39:13AM -0400, Doug Ledford wrote: > > > >> Let’s take this as a starting point. If there are other patches > >> people think should make 4.1, please bring them to my attention and > >> I’ll add them for review and possible addition to the list. > >> > >> git://github.com/dledford/linux.git for-4.1 > > > > I noticed a few patches didn't get Reviewed-By's etc from the mailing > > list annotated.. > > Every patch need not have a Reviewed-By annotation, it's perfectly up > to the maintainer judgement to make sure there was either consensus, More clearly: There were several patches where a Reviewed-By/etc was *provided* on-list but did not get captured in the git commit. AFAIK, capturing provided tags is considered best practice as a way to recognize and retain contributors. Jason -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Stepping down as maintainer (was Re: [PATCH for-next 0/9] mlx4 changes in virtual GID management)
On Thu, Apr 16, 2015 at 11:13 PM, Jason Gunthorpe wrote: > On Wed, Apr 15, 2015 at 08:39:13AM -0400, Doug Ledford wrote: > >> Let’s take this as a starting point. If there are other patches >> people think should make 4.1, please bring them to my attention and >> I’ll add them for review and possible addition to the list. >> >> git://github.com/dledford/linux.git for-4.1 > > I noticed a few patches didn't get Reviewed-By's etc from the mailing > list annotated.. Every patch need not have a Reviewed-By annotation, it's perfectly up to the maintainer judgement to make sure there was either consensus, or that he/she accepts that despite (say) one person not liking them -- here the 2nd type doesn't exist -- as Doug note spelled, these are the patches >> My IPoIB changes was reviewed by Erez >> Erez’s IPoIB changes was reviewed by Doug >> Or’s mlx4 changes these are Yishai's patches, driver ones, we applied your feedback BTW >> Sagi’s iSER changes posted by the driver maintainer, a co-maintainer (me) reviewed them >> The two patch fixup to the CVE issue have reviewed by >> A few other miscellaneous patches etc -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Stepping down as maintainer (was Re: [PATCH for-next 0/9] mlx4 changes in virtual GID management)
On Wed, Apr 15, 2015 at 08:39:13AM -0400, Doug Ledford wrote: > Let’s take this as a starting point. If there are other patches > people think should make 4.1, please bring them to my attention and > I’ll add them for review and possible addition to the list. > > git://github.com/dledford/linux.git for-4.1 I noticed a few patches didn't get Reviewed-By's etc from the mailing list annotated.. Jason -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: Stepping down as maintainer (was Re: [PATCH for-next 0/9] mlx4 changes in virtual GID management)
> -Original Message- > From: linux-rdma-ow...@vger.kernel.org > [mailto:linux-rdma-ow...@vger.kernel.org] On Behalf Of Doug Ledford > Sent: Monday, April 13, 2015 12:15 PM > To: Jason Gunthorpe > Cc: Yann Droneaud; Hefty, Sean; Roland Dreier; Hal Rosenstock > (h...@dev.mellanox.co.il); David Miller; Or Gerlitz; Weiny, Ira; linux- > r...@vger.kernel.org; ta...@mellanox.com; Amir Vadai; Sagi Grimberg; Haggai > Eran; Shachar Raindel > Subject: Re: Stepping down as maintainer (was Re: [PATCH for-next 0/9] mlx4 > changes in virtual GID management) > > > > On Apr 13, 2015, at 12:42 PM, Jason Gunthorpe > > wrote: > > > > On Sun, Apr 12, 2015 at 07:16:33PM +0200, Yann Droneaud wrote: > > > >> That would make sense to have someone like Doug or Jason being the > >> potential successors to Roland in order to keep InfiniBand subsystem > >> vendor neutrality. > > > > Several people have been asking me privately, I am looking into if > > this would be possible or not. > > > > Same here (having been asked privately to look into doing this). FWIW, Red > Hat has agreed that they are willing to allow me to transition > my job to a full time upstream focused position (as of now, I work on > upstream around my deliverables inside the company). > Doug, I think you're a good fit for the RDMA maintainer if you're willing. Steve. -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Stepping down as maintainer (was Re: [PATCH for-next 0/9] mlx4 changes in virtual GID management)
On Wed, Apr 15, 2015 at 8:13 PM, Roland Dreier wrote: > On Wed, Apr 15, 2015 at 5:39 AM, Doug Ledford wrote: >> Regardless of what we end up doing long term, Roland is out at the moment, >> so 4.1 is happening more or less without him :-/ > > Sorry. I am back at work now. > >> I went ahead and put together a 4.1 branch and pulled the patches I thought >> were ready. That’s been pushed to my github. > > Thanks, I will pick this up and put it in my kernel.org tree so we get > 0-day testing to make sure everything builds etc. Roland, see my "Re: RDMA patches for 4.1" note, there are two conflicts with net-next mlx4 commits. -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Stepping down as maintainer (was Re: [PATCH for-next 0/9] mlx4 changes in virtual GID management)
On Wed, Apr 15, 2015 at 5:39 AM, Doug Ledford wrote: > Regardless of what we end up doing long term, Roland is out at the moment, so > 4.1 is happening more or less without him :-/ Sorry. I am back at work now. > I went ahead and put together a 4.1 branch and pulled the patches I thought > were ready. That’s been pushed to my github. Thanks, I will pick this up and put it in my kernel.org tree so we get 0-day testing to make sure everything builds etc. - R. -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Stepping down as maintainer (was Re: [PATCH for-next 0/9] mlx4 changes in virtual GID management)
> On Apr 15, 2015, at 9:02 AM, Sagi Grimberg wrote: > > On 4/15/2015 3:39 PM, Doug Ledford wrote: >> >>> On Apr 15, 2015, at 7:43 AM, Pradeep Kankipati >>> wrote: >>> >>> We at Emulex, have been working with Doug on the RH inboxing effort for a >>> while and feel this just makes complete sense for him to take on this role >>> for all the reasons mentioned. Personally too I feel he is an excellent >>> choice. >> >> Regardless of what we end up doing long term, Roland is out at the moment, >> so 4.1 is happening more or less without him :-/ >> >> I went ahead and put together a 4.1 branch and pulled the patches I thought >> were ready. That’s been pushed to my github. I know it’s hard to get things >> done without being able to make sure your patches apply cleanly. For >> instance, the namespace patches aren’t included, and that’s at least >> partially because they didn’t apply cleanly any more. So, I included the >> following series of patches: >> >> My IPoIB changes >> Erez’s IPoIB changes >> Or’s mlx4 changes >> Sagi’s iSER changes > > Hey Doug, > > Did you pull v3? Yes. — Doug Ledford GPG Key ID: 0E572FDD signature.asc Description: Message signed with OpenPGP using GPGMail
Re: Stepping down as maintainer (was Re: [PATCH for-next 0/9] mlx4 changes in virtual GID management)
On 4/15/2015 4:07 PM, Doug Ledford wrote: On Apr 15, 2015, at 9:02 AM, Sagi Grimberg wrote: On 4/15/2015 3:39 PM, Doug Ledford wrote: On Apr 15, 2015, at 7:43 AM, Pradeep Kankipati wrote: We at Emulex, have been working with Doug on the RH inboxing effort for a while and feel this just makes complete sense for him to take on this role for all the reasons mentioned. Personally too I feel he is an excellent choice. Regardless of what we end up doing long term, Roland is out at the moment, so 4.1 is happening more or less without him :-/ I went ahead and put together a 4.1 branch and pulled the patches I thought were ready. That’s been pushed to my github. I know it’s hard to get things done without being able to make sure your patches apply cleanly. For instance, the namespace patches aren’t included, and that’s at least partially because they didn’t apply cleanly any more. So, I included the following series of patches: My IPoIB changes Erez’s IPoIB changes Or’s mlx4 changes Sagi’s iSER changes Hey Doug, Did you pull v3? Yes. Great, thanks. Sagi. -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Stepping down as maintainer (was Re: [PATCH for-next 0/9] mlx4 changes in virtual GID management)
On 4/15/2015 3:39 PM, Doug Ledford wrote: On Apr 15, 2015, at 7:43 AM, Pradeep Kankipati wrote: We at Emulex, have been working with Doug on the RH inboxing effort for a while and feel this just makes complete sense for him to take on this role for all the reasons mentioned. Personally too I feel he is an excellent choice. Regardless of what we end up doing long term, Roland is out at the moment, so 4.1 is happening more or less without him :-/ I went ahead and put together a 4.1 branch and pulled the patches I thought were ready. That’s been pushed to my github. I know it’s hard to get things done without being able to make sure your patches apply cleanly. For instance, the namespace patches aren’t included, and that’s at least partially because they didn’t apply cleanly any more. So, I included the following series of patches: My IPoIB changes Erez’s IPoIB changes Or’s mlx4 changes Sagi’s iSER changes Hey Doug, Did you pull v3? Sagi. -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Stepping down as maintainer (was Re: [PATCH for-next 0/9] mlx4 changes in virtual GID management)
> On Apr 15, 2015, at 7:43 AM, Pradeep Kankipati > wrote: > > We at Emulex, have been working with Doug on the RH inboxing effort for a > while and feel this just makes complete sense for him to take on this role > for all the reasons mentioned. Personally too I feel he is an excellent > choice. Regardless of what we end up doing long term, Roland is out at the moment, so 4.1 is happening more or less without him :-/ I went ahead and put together a 4.1 branch and pulled the patches I thought were ready. That’s been pushed to my github. I know it’s hard to get things done without being able to make sure your patches apply cleanly. For instance, the namespace patches aren’t included, and that’s at least partially because they didn’t apply cleanly any more. So, I included the following series of patches: My IPoIB changes Erez’s IPoIB changes Or’s mlx4 changes Sagi’s iSER changes The two patch fixup to the CVE issue A few other miscellaneous patches Let’s take this as a starting point. If there are other patches people think should make 4.1, please bring them to my attention and I’ll add them for review and possible addition to the list. git://github.com/dledford/linux.git for-4.1 > Thanks, > Pradeep > -- > > -Original Message- > From: linux-rdma-ow...@vger.kernel.org > [mailto:linux-rdma-ow...@vger.kernel.org] On Behalf Of ira.weiny > Sent: Wednesday, April 15, 2015 5:13 AM > To: Doug Ledford > Cc: Jason Gunthorpe; Yann Droneaud; Hefty, Sean; Roland Dreier; Hal > Rosenstock; David Miller; Or Gerlitz; linux-rdma@vger.kernel.org; > ta...@mellanox.com; Amir Vadai; Sagi Grimberg; Haggai Eran; Shachar Raindel > Subject: Re: Stepping down as maintainer (was Re: [PATCH for-next 0/9] mlx4 > changes in virtual GID management) > > On Mon, Apr 13, 2015 at 01:14:40PM -0400, Doug Ledford wrote: >> >>> On Apr 13, 2015, at 12:42 PM, Jason Gunthorpe > wrote: >>> >>> On Sun, Apr 12, 2015 at 07:16:33PM +0200, Yann Droneaud wrote: >>> >>>> That would make sense to have someone like Doug or Jason being the >>>> potential successors to Roland in order to keep InfiniBand >>>> subsystem vendor neutrality. >>> >>> Several people have been asking me privately, I am looking into if >>> this would be possible or not. >>> >> >> Same here (having been asked privately to look into doing this). >> FWIW, > Red Hat has agreed that they are willing to allow me to transition my job to > a full time upstream focused position (as of now, I work on upstream around > my deliverables inside the company). >> > > I think Doug and Jason are both qualified. > > However, with Red Hat willing to dedicate Doug full time I think that makes > Doug an ideal candidate considering the patch load. > > Ira > > -- > To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the > body of a message to majord...@vger.kernel.org More majordomo info at > http://vger.kernel.org/majordomo-info.html > — Doug Ledford GPG Key ID: 0E572FDD signature.asc Description: Message signed with OpenPGP using GPGMail
Re: Stepping down as maintainer (was Re: [PATCH for-next 0/9] mlx4 changes in virtual GID management)
On 4/13/2015 8:14 PM, Doug Ledford wrote: Same here (having been asked privately to look into doing this). FWIW, Red Hat has agreed that they are willing to allow me to transition my job to a full time upstream focused position (as of now, I work on upstream around my deliverables inside the company). Sounds very good. Doug, you've been around for long time and took active part in the evolution of this stack from the grounds and up to where we are today. Will be happy to see you picking the upstream maintainer seat for the for RDMA subsystem. Or. -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Stepping down as maintainer (was Re: [PATCH for-next 0/9] mlx4 changes in virtual GID management)
On Mon, Apr 13, 2015 at 01:14:40PM -0400, Doug Ledford wrote: > > > On Apr 13, 2015, at 12:42 PM, Jason Gunthorpe > > wrote: > > > > On Sun, Apr 12, 2015 at 07:16:33PM +0200, Yann Droneaud wrote: > > > >> That would make sense to have someone like Doug or Jason being the > >> potential successors to Roland in order to keep InfiniBand subsystem > >> vendor neutrality. > > > > Several people have been asking me privately, I am looking into if > > this would be possible or not. > > > > Same here (having been asked privately to look into doing this). FWIW, Red > Hat has agreed that they are willing to allow me to transition my job to a > full time upstream focused position (as of now, I work on upstream around my > deliverables inside the company). > I think Doug and Jason are both qualified. However, with Red Hat willing to dedicate Doug full time I think that makes Doug an ideal candidate considering the patch load. Ira -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Stepping down as maintainer (was Re: [PATCH for-next 0/9] mlx4 changes in virtual GID management)
On Sun, Apr 12, 2015 at 1:51 AM, Or Gerlitz wrote: > On Thu, Apr 9, 2015 at 8:41 PM, Roland Dreier wrote: >> On Tue, Apr 7, 2015 at 10:12 AM, Jason Gunthorpe >> wrote: >>> I don't think you understand how deep the problem Or is describing goes. > >>> [...Appropriate and correct critique...] > >> This thread has made me realize that even as I am able to carve out >> more time to work on things like IB maintaintership, I no longer have >> the desire to spend my time maintaining the IB subsystem. Since my >> current level of activity is clearly hurting the community, I've >> decided to step down as maintainer. > >> I'm on a perhaps-unfortunately-timed vacation this week > > OK, but this is the last time for making these excuses (...) > >> but to make the transition smooth, I'll handle the easy patches that are in >> flight >> for 4.1 and then turn things over to the community for 4.2 > > Sounds a fair plan to me. > > As we're just two days before the merge window is likely to open, > could you please but ASAP immediately make what's queued @ your > for-next branch private clone public?! Roland, So the merge window and there's still pretty much nothing in your for-next branch. Could you please comment what are those easy patches that you are going to put into the pull request for 4.1-rc1?! If you don't intend to send anything, please say it too. So we can send these already reviewed patches through other sub system maintainers. Or. > > currently, there's nothing there expect for one 4.- rc fix. > > Some from top of my head quick listing contains: > > 1. Doug's IPoIB patches which finally passed full review and > regression by Erez Shitrit @ Mellanox plus some review and testing by > Intel/Ira > http://marc.info/?t=14245649363&r=1&w=2 > > 2. Erez's followup patch series which few IPoIB changes and one mlx4 fix > http://marc.info/?l=linux-rdma&m=142797117721383&w=2 > > 3. Yishai's mlx4 patches (where we started this thread) > http://marc.info/?l=linux-rdma&m=142788688230585&w=2 > > 4. Sagi's iSER updates for 4.1 - which you acked but didn't make public > > Unfortunately, Sean -- you haven't provided for > 2 months any > feedback on the patches to the CM/CMA modules which you own/maintain > for supporting name-spaces and such which are part of enabling proper > RDMA support for containers. > http://marc.info/?l=linux-netdev&m=142366747608908&w=2 This makes your > co-maintainer position sort of problematic, BTW. Jason, any chance you > can look on > that? > > As for the core and driver RoCE changes, I see that there are comments > from Sean and Bart, so the review isn't over yet. -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Stepping down as maintainer (was Re: [PATCH for-next 0/9] mlx4 changes in virtual GID management)
On Mon, Apr 13, 2015 at 8:53 PM, Jason Gunthorpe wrote: > Or, I was also a bit annoyed by your last email, the tone just seemed > inappropriate/in-gracious for the situation. I made a full clarification and wait to see Sean's response. Sean is doing excellent work over the years, now something is on hold for months w.o any clear reason and I complain. -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Stepping down as maintainer (was Re: [PATCH for-next 0/9] mlx4 changes in virtual GID management)
On Mon, Apr 13, 2015 at 7:10 PM, Hefty, Sean wrote: >> Unfortunately, Sean -- you haven't provided for > 2 months any >> feedback on the patches to the CM/CMA modules which you own/maintain >> for supporting name-spaces and such which are part of enabling proper >> RDMA support for containers. >> http://marc.info/?l=linux-netdev&m=142366747608908&w=2 This makes your >> co-maintainer position sort of problematic, BTW. Jason, any chance you >> can look on that? > Linux does not pull anything from me directly. My own patches to the code > that I supposedly maintain take *years* to get upstream. I fail to see how > or why I need to review patches from a hostile party. Sure, I know that Linus doesn't pull directly from you and also that being a co-maintainer didn't help for when it took Roland 2-3 years to pick your AF_IB patch series. However, fact is that you are the author and maintainer of the CM and RDMA_CM and over the years Roland didn't pick patches to these components prior to your review and ack. > two months ago we sent patch series which serves to add RDMA support to > containers and modify these two drivers, and not a word from you. This is > what missing. In the past it took you two hours to provide excellent > feedback, now something is broken out. Sean, please speak up and explain who is hostile and why you think so, BTW is that a personal comment? Or. -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Stepping down as maintainer (was Re: [PATCH for-next 0/9] mlx4 changes in virtual GID management)
On Mon, Apr 13, 2015 at 8:53 PM, Jason Gunthorpe wrote: > As far as patches go, you keep asking for reviews, but where are the > reviews from Mellanox? I count 45 @mellanox folks who contributed to > the kernel, but I wouldn't have guessed that based on mailing > list participation. Jason, Making things more precise... glasses have two halves, namely: on the RDMA Storage side of things, Sagi Grimberg is doing tons of rdma kernel work, besides being a maintainer of both iSER target and Initiator drivers AND top contributor to both, he reviews practically every SRP patch sent to this list and many if not most of the NFS RDMA patches sent here. This can be checked with Bart Van Assche and Chuck Lever, see also [1] on the IPoIB side of things, Erez Shitrit is reviewing the IPoIB patches sent here. Specifically, he spent endless hours reviewing the 3-4 rounds of the fixes Doug sent in the last months, not only he reviewed them, he took them into regression on our systems and showed Doug again and again where things break, till the point where that worked. Hal Rosenstock is reviewing every patch which related to the MAD layer. Haggai Eran, Matan Barak and Shachar Raindel interacted with Yann on his comments and patches he sent to fix and enhance things around ODP and uverbs extensions. Jack Morgenstein, Eli Cohen and Amir Vadai constantly review patches and address questions and issues raised by other parties for the low-level mellanox drivers. ETC, and I will not speak on myself, see for yourself where/when I commented on patches sent by other members of this community. > I see patches from Yann, Michael, Ira, and Yuval at least on the list > that have seen general silence from your corner. That's just this last > month or so. Indeed, we can improve and some patch series didn't get enough review from a @mellanox.com person, but by all means, the volume of back reviews done here by mellanox folks goes way beyond what you describe. > Look - the only way a subsystem can function properly is if all > parties who want to continuously change the shared subystem core > realise they have to contribute back review-hours and discussion > leadership *AT LEAST* equal to what they receive. Or. [1] And all this is in parallel to his work @ the SCSI (previously MM too) subsystem (SCSI target, iSCSI stack, Block MQ, etc) which enables more indirect elements allowing for high performance RDMA storage to shine. -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: Stepping down as maintainer (was Re: [PATCH for-next 0/9] mlx4 changes in virtual GID management)
> Same here (having been asked privately to look into doing this). FWIW, > Red Hat has agreed that they are willing to allow me to transition my job > to a full time upstream focused position (as of now, I work on upstream > around my deliverables inside the company). Excellent. To me, this seems ideal. Doug, since you have the broadest testing, regardless of who reviews the patches, would you be willing to stage the upstream changes starting with 4.2? Does anyone (most importantly, Doug) have any issues with this?
Re: Stepping down as maintainer (was Re: [PATCH for-next 0/9] mlx4 changes in virtual GID management)
On Mon, Apr 13, 2015 at 04:10:16PM +, Hefty, Sean wrote: > > Unfortunately, Sean -- you haven't provided for > 2 months any > > feedback on the patches to the CM/CMA modules which you own/maintain > > for supporting name-spaces and such which are part of enabling proper > > RDMA support for containers. > > http://marc.info/?l=linux-netdev&m=142366747608908&w=2 This makes your > > co-maintainer position sort of problematic, BTW. Jason, any chance you > > can look on > > that? > > Linux does not pull anything from me directly. My own patches to > the code that I supposedly maintain take *years* to get upstream. I > fail to see how or why I need to review patches from a hostile > party. I expect the patch flow process will change.. We do actually need to all work together, so I urge you both to keep talking and hash something out. Or, I was also a bit annoyed by your last email, the tone just seemed inappropriate/in-gracious for the situation. As far as patches go, you keep asking for reviews, but where are the reviews from Mellanox? I count 45 @mellanox folks who contributed to the kernel, but I wouldn't have guessed that based on mailing list participation. I see patches from Yann, Michael, Ira, and Yuval at least on the list that have seen general silence from your corner. That's just this last month or so. Look - the only way a subsystem can function properly is if all parties who want to continuously change the shared subystem core realise they have to contribute back review-hours and discussion leadership *AT LEAST* equal to what they receive. Jason -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Stepping down as maintainer (was Re: [PATCH for-next 0/9] mlx4 changes in virtual GID management)
> On Apr 13, 2015, at 12:42 PM, Jason Gunthorpe > wrote: > > On Sun, Apr 12, 2015 at 07:16:33PM +0200, Yann Droneaud wrote: > >> That would make sense to have someone like Doug or Jason being the >> potential successors to Roland in order to keep InfiniBand subsystem >> vendor neutrality. > > Several people have been asking me privately, I am looking into if > this would be possible or not. > Same here (having been asked privately to look into doing this). FWIW, Red Hat has agreed that they are willing to allow me to transition my job to a full time upstream focused position (as of now, I work on upstream around my deliverables inside the company). — Doug Ledford GPG Key ID: 0E572FDD signature.asc Description: Message signed with OpenPGP using GPGMail
Re: Stepping down as maintainer (was Re: [PATCH for-next 0/9] mlx4 changes in virtual GID management)
On Sun, Apr 12, 2015 at 07:16:33PM +0200, Yann Droneaud wrote: > That would make sense to have someone like Doug or Jason being the > potential successors to Roland in order to keep InfiniBand subsystem > vendor neutrality. Several people have been asking me privately, I am looking into if this would be possible or not. Jason -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: Stepping down as maintainer (was Re: [PATCH for-next 0/9] mlx4 changes in virtual GID management)
> Unfortunately, Sean -- you haven't provided for > 2 months any > feedback on the patches to the CM/CMA modules which you own/maintain > for supporting name-spaces and such which are part of enabling proper > RDMA support for containers. > http://marc.info/?l=linux-netdev&m=142366747608908&w=2 This makes your > co-maintainer position sort of problematic, BTW. Jason, any chance you > can look on > that? Linux does not pull anything from me directly. My own patches to the code that I supposedly maintain take *years* to get upstream. I fail to see how or why I need to review patches from a hostile party.
Re: Stepping down as maintainer (was Re: [PATCH for-next 0/9] mlx4 changes in virtual GID management)
Hi, Le vendredi 10 avril 2015 à 20:39 +, Hefty, Sean a écrit : > > I'm on a perhaps-unfortunately-timed vacation this week, but to make > > the transition smooth, I'll handle the easy patches that are in flight > > for 4.1, and then turn things over to the community for 4.2. (Unless > > the feeling is that it's better for me to step down immediately — I > > have no problem doing that, I just don't want to leave people in the > > lurch) > > This transition plan makes sense to me. I can dedicate more of my > time helping to review kernel patches, at least for a couple of > months. Hal is listed as the other sub-maintainer. He usually limits > his input to the IB mgmt components, but maybe he can contribute more > until we're over this hump? > > I'm not trying to volunteer anyone, but longer term, Doug appears to > be in an ideal situation for maintaining the RDMA subtree. Because of > his position at RedHat, he has a strong interest in ensuring user > space compatibility, can test across a wide range of devices, and > needs to deal with long term maintenance issues. > That would make sense to have someone like Doug or Jason being the potential successors to Roland in order to keep InfiniBand subsystem vendor neutrality. Regards. -- Yann Droneaud OPTEYA -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Stepping down as maintainer (was Re: [PATCH for-next 0/9] mlx4 changes in virtual GID management)
On Thu, Apr 9, 2015 at 8:41 PM, Roland Dreier wrote: > On Tue, Apr 7, 2015 at 10:12 AM, Jason Gunthorpe > wrote: >> I don't think you understand how deep the problem Or is describing goes. >> [...Appropriate and correct critique...] > This thread has made me realize that even as I am able to carve out > more time to work on things like IB maintaintership, I no longer have > the desire to spend my time maintaining the IB subsystem. Since my > current level of activity is clearly hurting the community, I've > decided to step down as maintainer. > I'm on a perhaps-unfortunately-timed vacation this week OK, but this is the last time for making these excuses (...) > but to make the transition smooth, I'll handle the easy patches that are in > flight > for 4.1 and then turn things over to the community for 4.2 Sounds a fair plan to me. As we're just two days before the merge window is likely to open, could you please but ASAP immediately make what's queued @ your for-next branch private clone public?! currently, there's nothing there expect for one 4.- rc fix. Some from top of my head quick listing contains: 1. Doug's IPoIB patches which finally passed full review and regression by Erez Shitrit @ Mellanox plus some review and testing by Intel/Ira http://marc.info/?t=14245649363&r=1&w=2 2. Erez's followup patch series which few IPoIB changes and one mlx4 fix http://marc.info/?l=linux-rdma&m=142797117721383&w=2 3. Yishai's mlx4 patches (where we started this thread) http://marc.info/?l=linux-rdma&m=142788688230585&w=2 4. Sagi's iSER updates for 4.1 - which you acked but didn't make public Unfortunately, Sean -- you haven't provided for > 2 months any feedback on the patches to the CM/CMA modules which you own/maintain for supporting name-spaces and such which are part of enabling proper RDMA support for containers. http://marc.info/?l=linux-netdev&m=142366747608908&w=2 This makes your co-maintainer position sort of problematic, BTW. Jason, any chance you can look on that? As for the core and driver RoCE changes, I see that there are comments from Sean and Bart, so the review isn't over yet. Or. -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Stepping down as maintainer (was Re: [PATCH for-next 0/9] mlx4 changes in virtual GID management)
On Thu, Apr 9, 2015 at 9:06 PM, Hefty, Sean wrote: >> > This thread has made me realize that even as I am able to carve out >> > more time to work on things like IB maintaintership, I no longer >> > have the desire to spend my time maintaining the IB subsystem. >> > Since my current level of activity is clearly hurting the community, >> > I've decided to step down as maintainer. >> Thank you for all of your work over the years. I know that your >> technical skills and opinion have been widely appreciated and >> respected by the entire community. > I concur, and I'd like to thank you for the personal time that you dedicated > to this project. Here, too. Roland, you made a terrific job, specially over your 1st five years @ duty (...) pushing IB upstream in the form of a modern / modular and extendable kernel/user-space stack into Linux while designing it in a way which easily && elegantly allowed for bringing in more RDMA technologies such as RoCE and iWARP. I must also thank you personally for the tons of coaching and review comments you provided me over the years. If taking off the maintainer hat would get you some free/spare cycles, maybe you could resume posting in the digitalvampire blog and/or participate in the upstreamming of soft-RoCE driver? some folks here are working on this, so if you're interested, let me know... Or. -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Stepping down as maintainer (was Re: [PATCH for-next 0/9] mlx4 changes in virtual GID management)
On 4/9/15 10:41 AM, Roland Dreier wrote: On Tue, Apr 7, 2015 at 10:12 AM, Jason Gunthorpe wrote: I don't think you understand how deep the problem Or is describing goes. [...Appropriate and correct critique...] This thread has made me realize that even as I am able to carve out more time to work on things like IB maintaintership, I no longer have the desire to spend my time maintaining the IB subsystem. Since my current level of activity is clearly hurting the community, I've decided to step down as maintainer. Hi Roland, We have met a couple of times. I occasionally lurk on this list. Just wanted to pass on thanks for contributing so much over the years. You probably didn't know the impacts of much of your work, but its used extensively at NASA to do stuff like find planets around stars many light years away, build rocket ships, and understand the dynamics of the ocean. If you ever want to visit our facility in Mt View, let me know. Thank You. bob I'm on a perhaps-unfortunately-timed vacation this week, but to make the transition smooth, I'll handle the easy patches that are in flight for 4.1, and then turn things over to the community for 4.2. (Unless the feeling is that it's better for me to step down immediately — I have no problem doing that, I just don't want to leave people in the lurch) Thanks, Roland -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: Stepping down as maintainer (was Re: [PATCH for-next 0/9] mlx4 changes in virtual GID management)
> I'm on a perhaps-unfortunately-timed vacation this week, but to make
> the transition smooth, I'll handle the easy patches that are in flight
> for 4.1, and then turn things over to the community for 4.2. (Unless
> the feeling is that it's better for me to step down immediately — I
> have no problem doing that, I just don't want to leave people in the
> lurch)
This transition plan makes sense to me. I can dedicate more of my time helping
to review kernel patches, at least for a couple of months. Hal is listed as
the other sub-maintainer. He usually limits his input to the IB mgmt
components, but maybe he can contribute more until we're over this hump?
I'm not trying to volunteer anyone, but longer term, Doug appears to be in an
ideal situation for maintaining the RDMA subtree. Because of his position at
RedHat, he has a strong interest in ensuring user space compatibility, can test
across a wide range of devices, and needs to deal with long term maintenance
issues.
- Sean
N�r��yb�X��ǧv�^�){.n�+{��ٚ�{ay� ʇڙ�,j��f���h���z� �w���
���j:+v���w�j�mzZ+�ݢj"��!�i
Re: Stepping down as maintainer (was Re: [PATCH for-next 0/9] mlx4 changes in virtual GID management)
On Thu, 2015-04-09 at 10:41 -0700, Roland Dreier wrote: > On Tue, Apr 7, 2015 at 10:12 AM, Jason Gunthorpe > wrote: > > I don't think you understand how deep the problem Or is describing > > goes. > > > [...Appropriate and correct critique...] > > This thread has made me realize that even as I am able to carve out > more time to work on things like IB maintaintership, I no longer have > the desire to spend my time maintaining the IB subsystem. Since my > current level of activity is clearly hurting the community, I've > decided to step down as maintainer. Thank you for the long, thankless years of service. I wish you the best in whatever endeavors you choose to focus on! -- Doug Ledford GPG KeyID: 0E572FDD signature.asc Description: This is a digitally signed message part
Re: Stepping down as maintainer (was Re: [PATCH for-next 0/9] mlx4 changes in virtual GID management)
Hi Roland, Le jeudi 09 avril 2015 à 18:06 +, Hefty, Sean a écrit : > > > This thread has made me realize that even as I am able to carve out > > > more time to work on things like IB maintaintership, I no longer > > > have the desire to spend my time maintaining the IB subsystem. > > > Since my current level of activity is clearly hurting the community, > > > I've decided to step down as maintainer. > > > > Thank you for all of your work over the years. I know that your > > technical skills and opinion have been widely appreciated and > > respected by the entire community. > > I concur, and I'd like to thank you for the personal time that you dedicated > to this project. Thank you for all your work ! Anyway, I hope you will keep contributing to the kernel and userspace parts of the InfiniBand/RDMA subsystem. Best regards. -- Yann Droneaud OPTEYA -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: Stepping down as maintainer (was Re: [PATCH for-next 0/9] mlx4 changes in virtual GID management)
>
> On Tue, Apr 7, 2015 at 10:12 AM, Jason Gunthorpe
> wrote:
> > I don't think you understand how deep the problem Or is describing
> > goes.
>
> > [...Appropriate and correct critique...]
>
> This thread has made me realize that even as I am able to carve out more time
> to work on things like IB maintaintership, I no longer have the desire to
> spend
> my time maintaining the IB subsystem. Since my current level of activity is
> clearly hurting the community, I've decided to step down as maintainer.
>
I am sad to see you leave. Without you InfiniBand would have never been
accepted upstream at all.
Thank you for all the hard work,
Ira
N�r��yb�X��ǧv�^�){.n�+{��ٚ�{ay� ʇڙ�,j��f���h���z� �w���
���j:+v���w�j�mzZ+�ݢj"��!�i
RE: Stepping down as maintainer (was Re: [PATCH for-next 0/9] mlx4 changes in virtual GID management)
> > This thread has made me realize that even as I am able to carve out > > more time to work on things like IB maintaintership, I no longer > > have the desire to spend my time maintaining the IB subsystem. > > Since my current level of activity is clearly hurting the community, > > I've decided to step down as maintainer. > > Thank you for all of your work over the years. I know that your > technical skills and opinion have been widely appreciated and > respected by the entire community. I concur, and I'd like to thank you for the personal time that you dedicated to this project. -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Stepping down as maintainer (was Re: [PATCH for-next 0/9] mlx4 changes in virtual GID management)
On Thu, Apr 09, 2015 at 10:41:13AM -0700, Roland Dreier wrote: > This thread has made me realize that even as I am able to carve out > more time to work on things like IB maintaintership, I no longer > have the desire to spend my time maintaining the IB subsystem. > Since my current level of activity is clearly hurting the community, > I've decided to step down as maintainer. Thank you for all of your work over the years. I know that your technical skills and opinion have been widely appreciated and respected by the entire community. Regards, Jason -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Stepping down as maintainer (was Re: [PATCH for-next 0/9] mlx4 changes in virtual GID management)
On Tue, Apr 7, 2015 at 10:12 AM, Jason Gunthorpe wrote: > I don't think you understand how deep the problem Or is describing > goes. > [...Appropriate and correct critique...] This thread has made me realize that even as I am able to carve out more time to work on things like IB maintaintership, I no longer have the desire to spend my time maintaining the IB subsystem. Since my current level of activity is clearly hurting the community, I've decided to step down as maintainer. I'm on a perhaps-unfortunately-timed vacation this week, but to make the transition smooth, I'll handle the easy patches that are in flight for 4.1, and then turn things over to the community for 4.2. (Unless the feeling is that it's better for me to step down immediately — I have no problem doing that, I just don't want to leave people in the lurch) Thanks, Roland -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
