All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Pavel Machek <pavel@ucw.cz>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -mm] swsusp: userland interface (rev 2)
Date: Wed, 25 Jan 2006 00:53:26 +0100	[thread overview]
Message-ID: <200601250053.27394.rjw@sisk.pl> (raw)
In-Reply-To: <20060124221426.GB1602@elf.ucw.cz>

Hi,

On Tuesday, 24 January 2006 23:14, Pavel Machek wrote:
> > > > > This patch introduces a user space interface for swsusp.
> > > > 
> > > > How will we know if/when this feature is ready for mainline?  What criteria
> > > > can we use to judge that?
> > > 
> > > It was stable for me last time I tested. I do not think it needs
> > > longer -mm testing than usual patches.
> > 
> > One we've shipped the interface we're kinda stuck with it for ever, so it
> > does want to be pretty mature.
> 
> Well, I think we got the interface pretty much right -- and it is
> really pretty simple. It survived pretty nasty stress testing at one
> point.

I think the ioctls defined so far won't change.  However, it's possible we'll
need some more (for example the suspend console handling is not
optimal now, so to speak).

IMHO the current version is sufficient to start with, but now we should
start working on userland tools seriously.  Then it'll turn out what else
is necessary.

> Of course, bad things happen. Having it merged but disabled in
> Makefile would certainly be preferred than not merged at
> all. Plus... stable kernel or not, it is new feature, and userland
> suspending programs are quite closely tied to the kernel. I think it
> is reasonable to expect users to have matching version of kernel and
> userland-swsusp tools, at least before dust settles.

I'm afraid that would be a nightmare for distributors who decide to use it.

IMHO after it gets into mainline every next version of the interface should
be backwards compatible with the previous one.

Greetings,
Rafael

  parent reply	other threads:[~2006-01-25  0:11 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-24  8:29 [PATCH -mm] swsusp: userland interface (rev 2) Rafael J. Wysocki
2006-01-24 11:14 ` Pavel Machek
2006-01-24 21:13 ` Andrew Morton
2006-01-24 21:30   ` Pavel Machek
2006-01-24 21:58     ` Andrew Morton
2006-01-24 22:14       ` Pavel Machek
2006-01-24 22:20         ` Dave Jones
2006-01-24 22:33           ` Pavel Machek
2006-01-24 22:38             ` Dave Jones
2006-01-24 22:44               ` Pavel Machek
2006-01-26  2:09                 ` Jim Crilly
2006-01-26  7:58                   ` Pavel Machek
2006-01-27  1:11                   ` Greg KH
2006-01-27  3:42                   ` Kay Sievers
2006-01-27 11:24                     ` Rafael J. Wysocki
2006-01-24 22:47               ` Lee Revell
2006-01-24 23:53         ` Rafael J. Wysocki [this message]
2006-01-25  0:17           ` Andrew Morton
2006-01-25  0:31             ` Rafael J. Wysocki
2006-01-24 23:35   ` Rafael J. Wysocki
2006-01-25  2:46     ` Benjamin LaHaise
2006-01-25 10:50       ` Rafael J. Wysocki
2006-01-25 12:18     ` Pavel Machek
2006-01-25 12:29       ` Rafael J. Wysocki
2006-01-25 12:20     ` Pavel Machek

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=200601250053.27394.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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.