public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-pm@lists.osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH/rfc] schedule /sys/device/.../power for removal
Date: Sat, 13 May 2006 22:43:22 +0200	[thread overview]
Message-ID: <20060513204322.GB585@elf.ucw.cz> (raw)
In-Reply-To: <20060512032702.3591289f.akpm@osdl.org>

[-- Attachment #1: Type: text/plain, Size: 1436 bytes --]

Hi!

> > > > index 421bcff..dfcfc47 100644
> > > > --- a/Documentation/feature-removal-schedule.txt
> > > > +++ b/Documentation/feature-removal-schedule.txt
> > > > @@ -6,6 +6,16 @@ be removed from this file.
> > > >  
> > > >  ---------------------------
> > > >  
> > > > +What:	/sys/device/.../power
> > > > +When:	July 2007
> > > > +Files:	
> > > > +Why:	Because it takes integers, and different userland applications
> > > > +	expect different numbers to mean different things.
> > > > +	(Pcmcia expect 2 for off, some other code expects 3 for off).
> > > > +Who:	Pavel Machek <pavel@suse.cz>
> > > > +
> > > > +---------------------------
> > > 
> > > What will be impacted by this?
> > 
> > Some obscure place PCMCIA utils, IIRC. There was one more user, but I
> > do not remember who it was. Plus there may be few people doing echo
> > manually.
> 
> What will it be replaced with, and how will we communicate the need to
> migrate to the various application developers?  We can't just rip it out
> next year and point at some obscure entry in a kernel file and say "but we
> told you".

Ok, we do not have replacement ready, yet. Would it be feasible to
include warning now so that people are warned as early as possible,
while we are working on replacement? Ok, maybe not...
								Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2006-05-13 20:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-12 10:05 [PATCH/rfc] schedule /sys/device/.../power for removal Pavel Machek
2006-05-12 10:11 ` Andrew Morton
2006-05-12 10:19   ` Pavel Machek
2006-05-12 10:27     ` Andrew Morton
2006-05-13 20:43       ` Pavel Machek [this message]
2006-05-12 13:52   ` [linux-pm] " David Brownell
2006-05-14  0:13     ` Benjamin Herrenschmidt
2006-05-14 15:51       ` David Brownell
2006-05-14 16:22         ` Pavel Machek
2006-05-14 17:45           ` David Brownell
2006-05-14  0:21     ` Benjamin Herrenschmidt
2006-05-14 17:48       ` David Brownell
2006-05-14 23:56         ` Benjamin Herrenschmidt

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=20060513204322.GB585@elf.ucw.cz \
    --to=pavel@suse.cz \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.osdl.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