All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Linux PM <linux-pm@osdl.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC/RFT][PATCH -mm 0/5] swsusp: userland interface (rev. 2)
Date: Fri, 6 Jan 2006 23:44:30 +0100	[thread overview]
Message-ID: <20060106224430.GC12428@elf.ucw.cz> (raw)
In-Reply-To: <200601062217.09012.rjw@sisk.pl>

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

Hi!

> > > This is the second "preview release" of the swsusp userland interface patches.
> > > They have changed quite a bit since the previous post, as I tried to make the
> > > interface more robust against some potential user space bugs (or outright
> > > attempts to abuse it).
> > 
> > Works for me, thanks.
> > 
> > Perhaps it is time to get 1/4 and 3/4 into -mm? You get my signed-off
> > on them...
> 
> OK, I'll prepare them in a while.

Thanks.

> > 2/4 needs to allocate official major/minor. 1/13 would be nice :-).
> 
> Well, you said you liked the patch with a misc device (ie. major = 10).
> 
> Actually the code is somewhat simpler in that case so I'd prefer it.
> 
> Now, if we used a misc device, which minor would be suitable?  231?

If code is simpler, lets stick with misc. You have to obtain minor by
mailing device@lanana.org, see Doc*/devices.txt.

> > 4/4... I'm not sure. It would be nice to make swsusp.c disappear. It
> > is really wrong name. That means we need to only delete from it for a
> > while...
> 
> Anyway I think it would be nice to move the code that does not really belong
> to the snapshot and is used by both the user interface and disk.c/swap.c to
> a separate file.  I have no preference as far as the name of the file is
> concerned, though.

Ok, lets keep it as it is. We can always rename file in future. [I
don't quite understand your reasons for movement, through. Highmem is
part of snapshot we need to make; it is saved in a very different way
than rest of memory, but that is implementation detail...]


									Pavel
-- 
Thanks, Sharp!

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



WARNING: multiple messages have this Message-ID (diff)
From: Pavel Machek <pavel@ucw.cz>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Linux PM <linux-pm@osdl.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC/RFT][PATCH -mm 0/5] swsusp: userland interface (rev. 2)
Date: Fri, 6 Jan 2006 23:44:30 +0100	[thread overview]
Message-ID: <20060106224430.GC12428@elf.ucw.cz> (raw)
In-Reply-To: <200601062217.09012.rjw@sisk.pl>

Hi!

> > > This is the second "preview release" of the swsusp userland interface patches.
> > > They have changed quite a bit since the previous post, as I tried to make the
> > > interface more robust against some potential user space bugs (or outright
> > > attempts to abuse it).
> > 
> > Works for me, thanks.
> > 
> > Perhaps it is time to get 1/4 and 3/4 into -mm? You get my signed-off
> > on them...
> 
> OK, I'll prepare them in a while.

Thanks.

> > 2/4 needs to allocate official major/minor. 1/13 would be nice :-).
> 
> Well, you said you liked the patch with a misc device (ie. major = 10).
> 
> Actually the code is somewhat simpler in that case so I'd prefer it.
> 
> Now, if we used a misc device, which minor would be suitable?  231?

If code is simpler, lets stick with misc. You have to obtain minor by
mailing device@lanana.org, see Doc*/devices.txt.

> > 4/4... I'm not sure. It would be nice to make swsusp.c disappear. It
> > is really wrong name. That means we need to only delete from it for a
> > while...
> 
> Anyway I think it would be nice to move the code that does not really belong
> to the snapshot and is used by both the user interface and disk.c/swap.c to
> a separate file.  I have no preference as far as the name of the file is
> concerned, though.

Ok, lets keep it as it is. We can always rename file in future. [I
don't quite understand your reasons for movement, through. Highmem is
part of snapshot we need to make; it is saved in a very different way
than rest of memory, but that is implementation detail...]


									Pavel
-- 
Thanks, Sharp!

  reply	other threads:[~2006-01-06 22:44 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-04 22:40 [RFC/RFT][PATCH -mm 0/5] swsusp: userland interface (rev. 2) Rafael J. Wysocki
2006-01-04 22:40 ` Rafael J. Wysocki
2006-01-04 22:47 ` [RFC/RFT][PATCH -mm 1/5] swsusp: swsusp: low level " Rafael J. Wysocki
2006-01-04 22:51 ` [RFC/RFT][PATCH -mm 2/5] swsusp: userland " Rafael J. Wysocki
2006-01-04 22:51   ` Rafael J. Wysocki
2006-01-04 23:49   ` [linux-pm] " Greg KH
2006-01-05  0:18     ` Pavel Machek
2006-01-05  0:18       ` [linux-pm] " Pavel Machek
2006-01-05  0:26       ` Greg KH
2006-01-05  0:26         ` [linux-pm] " Greg KH
2006-01-05  0:54         ` Pavel Machek
2006-01-05  0:54           ` [linux-pm] " Pavel Machek
2006-01-05  0:55         ` Pavel Machek
2006-01-05  0:55           ` [linux-pm] " Pavel Machek
2006-01-05 23:34         ` Rafael J. Wysocki
2006-01-05 23:34           ` [linux-pm] " Rafael J. Wysocki
2006-01-05 23:45           ` Greg KH
2006-01-05 23:45             ` [linux-pm] " Greg KH
2006-01-04 22:53 ` [RFC/RFT][PATCH -mm 3/5] swsusp: separate swap-writing and reading code " Rafael J. Wysocki
2006-01-04 22:53   ` Rafael J. Wysocki
2006-01-04 22:55 ` [RFC/RFT][PATCH -mm 4/5] swsusp: move highmem-handling code to swsusp.c " Rafael J. Wysocki
2006-01-04 22:55   ` Rafael J. Wysocki
2006-01-04 22:56 ` [RFC/RFT][PATCH -mm 5/5] swsusp: userland interface documentation and config Rafael J. Wysocki
2006-01-04 22:56   ` Rafael J. Wysocki
2006-01-05  1:05 ` [RFC/RFT][PATCH -mm 0/5] swsusp: userland interface (rev. 2) Pavel Machek
2006-01-05  1:05   ` Pavel Machek
2006-01-05 23:30 ` Pavel Machek
2006-01-06 21:17   ` Rafael J. Wysocki
2006-01-06 22:44     ` Pavel Machek [this message]
2006-01-06 22:44       ` Pavel Machek
2006-01-06 23:41       ` Rafael J. Wysocki
2006-01-06 23:59         ` 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=20060106224430.GC12428@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@osdl.org \
    --cc=rjw@sisk.pl \
    /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.