Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932202AbbGCNZi (ORCPT ); Fri, 3 Jul 2015 09:25:38 -0400 Received: from mga11.intel.com ([192.55.52.93]:46387 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755130AbbGCNZ3 convert rfc822-to-8bit (ORCPT ); Fri, 3 Jul 2015 09:25:29 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.15,400,1432623600"; d="scan'208";a="518407784" From: "Dalessandro, Dennis" To: Greg Kroah-Hartman , "Luis R. Rodriguez" CC: "Marciniszyn, Mike" , Borislav Petkov , Ingo Molnar , One Thousand Gnomes , Doug Ledford , "linux-rdma@vger.kernel.org" , "linux-kernel@vger.kernel.org" Subject: RE: Deprecating ipath Thread-Topic: Deprecating ipath Thread-Index: AdCwK32HisMkMAzZQxSk4PS5RnApHgAMztqAAAERSoABS565EA== Date: Fri, 3 Jul 2015 13:25:25 +0000 Message-ID: References: <32E1700B9017364D9B60AED9960492BC257567C3@fmsmsx120.amr.corp.intel.com> <20150626165401.GA14699@kroah.com> In-Reply-To: <20150626165401.GA14699@kroah.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.18.205.10] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2182 Lines: 58 > -----Original Message----- > From: linux-rdma-owner@vger.kernel.org [mailto:linux-rdma- > owner@vger.kernel.org] On Behalf Of Greg Kroah-Hartman > Sent: Friday, June 26, 2015 12:54 PM > To: Luis R. Rodriguez > Cc: Marciniszyn, Mike; Borislav Petkov; Ingo Molnar; One Thousand Gnomes; > Doug Ledford; linux-rdma@vger.kernel.org; linux-kernel@vger.kernel.org > Subject: Re: Deprecating ipath > > On Fri, Jun 26, 2015 at 09:23:27AM -0700, Luis R. Rodriguez wrote: > > On Fri, Jun 26, 2015 at 9:17 AM, Marciniszyn, Mike > > wrote: > > > Doug, > > > > > > We have been given the go ahead to start the deprecation process for > thie ipath driver. > > > > That's great! Do you mean removal from Linux? > > > > > What do I need to do to get that done? > > > > Feature removal txt file was removed from the kernel so there is no > > "schedule" per se, not sure what the process these days is for driver > > removal. How about punting it to staging for a release or two and then > > remove it? Not sure if that would be frowned upon or welcomed. > > That is the process for driver removal, so of course it is welcomed :) > > > That would have the cost of moving history through directories but git > > --follow helps with that these days. The gain of moving it to staging > > IMHO would be that if anyone who might care would need to complain > may > > do so for a directory change for 1-2 release may spot this easily and > > the issues would be much less than an immediate removal. > > Yes, that's why we do it this way. > > Mike, feel free to send me a patch for this if you want me to queue it up for > 4.3. For 4.2 it's too late. > > thanks, > > greg k-h > -- Greg, how would you like to consume that patch? There are a number of large files. We can break things up into a series and send through email. We could also post a repo somewhere that you can do a pull from. Something else? Thanks -Denny -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/