All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: boris.ostrovsky@oracle.com, david.vrabel@citrix.com,
	ksummit-discuss@lists.linuxfoundation.org,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: [Ksummit-discuss] Topic: Removal of code that is still in use by users but there is a better code.
Date: Wed, 11 Jun 2014 10:54:33 -0700	[thread overview]
Message-ID: <20140611175433.GA10462@roeck-us.net> (raw)
In-Reply-To: <53976840.40306@zytor.com>

On Tue, Jun 10, 2014 at 01:19:12PM -0700, H. Peter Anvin wrote:
> On 06/10/2014 01:12 PM, Konrad Rzeszutek Wilk wrote:
> > Hey,
> > 
> > I would want to propose a topic on removing code in Linux that
> > users are using - but they are doing it less and less and it
> > mostly is tied in with older hardware. Specifically how to do
> > this transition properly - and if we want to define some checklist
> > /policy to do it via.
> > 
> 
> I second this.  Right now deprecation is entirely ad hoc... usually in
> the form "this hasn't compiled for X releases and noone noticed", which
> makes it hard to do *controlled* deprecation...
> 
That is a bit different to "users are using but less and less". Personally 
I would not mind leaving code in the kernel as long as it is used, but
it would be great if we had some rule that a file/driver which did
not compile for X releases (pick a preferred number for X - two years 
worth of releases ?) can be removed.

Guenter

  parent reply	other threads:[~2014-06-11 17:54 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-10 20:12 [Ksummit-discuss] Topic: Removal of code that is still in use by users but there is a better code Konrad Rzeszutek Wilk
2014-06-10 20:19 ` H. Peter Anvin
2014-06-11  0:36   ` josh
2014-06-11 15:56     ` H. Peter Anvin
2014-06-11 20:02       ` josh
2014-06-11 17:54   ` Guenter Roeck [this message]
2014-06-11 19:43     ` Bjorn Helgaas
2014-06-11 21:53       ` Stephen Rothwell
2014-06-11 22:01         ` Andy Lutomirski
2014-06-11 22:17           ` James Bottomley
2014-06-11 22:26             ` Roland Dreier
2014-06-11 22:36               ` James Bottomley
2014-06-12 11:41                 ` Rafael J. Wysocki
2014-06-12 13:27                 ` John W. Linville
2014-06-13  1:36                   ` James Bottomley
2014-06-19 13:01                 ` Linus Walleij
2014-06-11 23:22       ` Guenter Roeck
2014-06-12  2:48         ` Steven Rostedt
2014-06-12  7:16           ` Geert Uytterhoeven
2014-06-12  0:07     ` H. Peter Anvin

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=20140611175433.GA10462@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=boris.ostrovsky@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=hpa@zytor.com \
    --cc=konrad.wilk@oracle.com \
    --cc=ksummit-discuss@lists.linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.