From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Luis R. Rodriguez" <mcgrof@suse.com>
Cc: "Marciniszyn, Mike" <mike.marciniszyn@intel.com>,
Borislav Petkov <bp@suse.de>, Ingo Molnar <mingo@kernel.org>,
One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>,
Doug Ledford <dledford@redhat.com>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Deprecating ipath
Date: Fri, 26 Jun 2015 09:54:01 -0700 [thread overview]
Message-ID: <20150626165401.GA14699@kroah.com> (raw)
In-Reply-To: <CAB=NE6WTPKUF3EUVk6Z91pd+PYTjLdrLHr0Gn=n9+Z98cVdPWg@mail.gmail.com>
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
> <mike.marciniszyn@intel.com> 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
next prev parent reply other threads:[~2015-06-26 16:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <32E1700B9017364D9B60AED9960492BC257567C3@fmsmsx120.amr.corp.intel.com>
2015-06-26 16:23 ` Deprecating ipath Luis R. Rodriguez
2015-06-26 16:54 ` Greg Kroah-Hartman [this message]
2015-07-03 13:25 ` Dalessandro, Dennis
2015-07-03 15:36 ` Greg Kroah-Hartman
2015-07-03 17:18 ` Luis R. Rodriguez
2015-07-03 17:19 ` Luis R. Rodriguez
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150626165401.GA14699@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bp@suse.de \
--cc=dledford@redhat.com \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mcgrof@suse.com \
--cc=mike.marciniszyn@intel.com \
--cc=mingo@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox