All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Lutomirski <luto@amacapital.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	David Vrabel <david.vrabel@citrix.com>,
	"ksummit-discuss@lists.linuxfoundation.org"
	<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 15:01:48 -0700	[thread overview]
Message-ID: <CALCETrXEZ-Z+Kqgs28RCe7r9M-+QhbR2tQdMtznDB2uwmSmvYA@mail.gmail.com> (raw)
In-Reply-To: <20140612075355.4b0d1f5a@canb.auug.org.au>

On Wed, Jun 11, 2014 at 2:53 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi Bjorn,
>
> On Wed, 11 Jun 2014 13:43:18 -0600 Bjorn Helgaas <bhelgaas@google.com> wrote:
>>
>> all did our jobs perfectly, we would never add a change to Linux that
>> broke compilation of anything.  So if there's a file that doesn't
>> compile anymore, I think of that as a result of a mistake somewhere
>> along the line.  We can use that mistake to deduce that nobody cares
>> anymore, but it'd be a lot nicer to have a scheme that didn't depend
>> on people making random mistakes.
>
> We could start making nonrandom mistakes? ;-)

How about adding CONFIG_DELETED_THINGS.  If you enable it, you get a
message asking you to speak up if you actually need anything in there.
CONFIG_DELETED_THINGS would default to n, and the new (and temporary)
things under it would also default to n.

Think feature-removal-schedule, but with teeth.

--Andy

  reply	other threads:[~2014-06-11 22:02 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
2014-06-11 19:43     ` Bjorn Helgaas
2014-06-11 21:53       ` Stephen Rothwell
2014-06-11 22:01         ` Andy Lutomirski [this message]
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=CALCETrXEZ-Z+Kqgs28RCe7r9M-+QhbR2tQdMtznDB2uwmSmvYA@mail.gmail.com \
    --to=luto@amacapital.net \
    --cc=boris.ostrovsky@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=konrad.wilk@oracle.com \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=sfr@canb.auug.org.au \
    /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.