public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Len Brown <lenb@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	x86@kernel.org, linux-pm@lists.linux-foundation.org,
	linux-kernel@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] x86 APM: delete Linux kernel APM support
Date: Mon, 28 Mar 2011 07:18:41 +0200	[thread overview]
Message-ID: <20110328051841.GA1342@elte.hu> (raw)
In-Reply-To: <alpine.LFD.2.02.1103260036300.28928@x980>


* Len Brown <lenb@kernel.org> wrote:

> > .42 removal might be too fast, considering the typical release schedule of 
> > Linux distributions. And i'm still doubting the removal itself: we are 
> > adding lots of special-purpose subarch drivers to arch/x86/ as we speak 
> > (the embedded mess coming to x86) - which drivers will be tomorrow's APM 
> > code. On what grounds do we treat APM support differently?
> >
> > Our general compatibility with old hardware is an *asset* that we should value.
> 
> My guess is that the customers have died off,

How do we know that? Users are on a bell curve, with a fat tail. If stuff just 
works - and that's not unexpected from relatively simple (and most likely to be 
used) APM functionality like APM-poweroff, why should they ever report 
problems?

Removing a driver based on lack of visible feedback is like removing 190,000 
apps from a 200,000 apps app store, on the (valid) observation that the top 
1000 apps receive 99% of the traffic and use so the remaining 1% are just a 
maintenance burden.

There's value in the concept of knowing that we do not do forced obscolescence 
in Linux and there's a value in a very broad "there's a driver for that" 
concept, just like there's value in a very broad "there's an app for that" 
concept.

> and so the code is no longer an asset, but a maintenance liability.
> 
> If there is a buzzing community of people running 2011
> linux kernels on their ancient laptops in APM mode,
> then the APM maintainer would probably know about them.

Not if most of them use APM-poweroff. I think i even had a desktop box (not a 
laptop) that supported APM suspend (or am i mistaken there, was APM suspend 
support only limited to laptops?).

Thanks,

	Ingo

  parent reply	other threads:[~2011-03-28  5:19 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <alpine.LFD.2.02.1103232321070.3848@x980>
     [not found] ` <20110324154505.934a56a0.sfr@canb.auug.org.au>
2011-03-24  7:39   ` [PATCH] APM: delete APM in Linux-2.6.40 Len Brown
2011-03-24  8:16     ` [PATCH] x86 APM: delete Linux kernel APM support Len Brown
2011-03-24  8:31       ` [PATCH] x86 APM: delete Linux kernel APM support (v2) Len Brown
2011-03-24 16:01         ` Andi Kleen
2011-03-24  8:39       ` [PATCH] x86 APM: delete Linux kernel APM support Ingo Molnar
2011-03-24 23:49         ` Len Brown
2011-03-25 11:30           ` Ingo Molnar
2011-03-25 12:38             ` Ingo Molnar
2011-03-25 12:41               ` Ingo Molnar
2011-03-25 22:33             ` Rafael J. Wysocki
2011-03-26  4:35               ` Len Brown
2011-04-08  6:25               ` Pavel Machek
2011-04-08 20:55                 ` H. Peter Anvin
2011-04-11 13:05                   ` Pavel Machek
2011-04-11 18:19                     ` H. Peter Anvin
2011-04-13 13:30                       ` Pavel Machek
2011-03-26  5:01             ` Len Brown
2011-03-26  9:31               ` Ingo Molnar
2011-03-27 21:40               ` Ondrej Zary
2011-03-28  4:51                 ` Ingo Molnar
2011-03-28  5:43                   ` H. Peter Anvin
2011-03-28 12:57                 ` H. Peter Anvin
2011-03-28  5:18               ` Ingo Molnar [this message]
2011-03-25 15:41           ` Calvin Walton
2011-03-24  8:18     ` [PATCH] APM: delete APM in Linux-2.6.40 Stephen Rothwell
2011-03-24  8:38     ` Alexander Stein
2011-03-24 10:21     ` Henrique de Moraes Holschuh
2011-03-24 23:05       ` Len Brown
2011-03-25  1:07         ` Henrique de Moraes Holschuh
2011-03-25  1:34           ` Len Brown
2011-04-04 16:44           ` Pavel Machek
2011-04-04 20:18             ` Len Brown
2011-03-24 12:15     ` Ondrej Zary
2011-03-24 23:29       ` Len Brown
2011-03-25  8:07         ` Ondrej Zary
2011-03-26  5:09           ` Len Brown
2011-04-02 21:40     ` Yuhong Bao

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=20110328051841.GA1342@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=hpa@zytor.com \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=sfr@canb.auug.org.au \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@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