From: Steven Rostedt <rostedt@goodmis.org>
To: Guenter Roeck <linux@roeck-us.net>
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 22:48:42 -0400 [thread overview]
Message-ID: <20140611224842.2a011256@gandalf.local.home> (raw)
In-Reply-To: <5398E4A8.9080200@roeck-us.net>
On Wed, 11 Jun 2014 16:22:16 -0700
Guenter Roeck <linux@roeck-us.net> wrote:
>
> I understand, but personally I don't have much problem with code as long
> as it compiles. I am more concerned with code that doesn't compile and
> no one cared for years.
Matters what your definition of "doesn't compile" is.
You may not have the right config option set to make it compile.
randconfig builds trigger failed compiles quite often. Is that code
worth removing?
As most people test allyesconfig and allmodconfig quite a bit, I'm not
sure what code you are talking about. Basically everything that gets
enabled does compile.
Of course, if you set something to CONFIG_BROKEN and no one complains
for a few years, that's worth nuking.
-- Steve
next prev parent reply other threads:[~2014-06-12 2:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-10 20:12 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
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 [this message]
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=20140611224842.2a011256@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=linux@roeck-us.net \
/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