From: Greg KH <greg@kroah.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Linux PM <linux-pm@osdl.org>, LKML <linux-kernel@vger.kernel.org>,
Pavel Machek <pavel@ucw.cz>
Subject: Re: [RFC/RFT][PATCH -mm 2/5] swsusp: userland interface (rev. 2)
Date: Thu, 5 Jan 2006 15:45:28 -0800 [thread overview]
Message-ID: <20060105234528.GA28365@kroah.com> (raw)
In-Reply-To: <200601060034.53707.rjw@sisk.pl>
[-- Attachment #1: Type: text/plain, Size: 309 bytes --]
On Fri, Jan 06, 2006 at 12:34:52AM +0100, Rafael J. Wysocki wrote:
> > Ok, then I'd recommend using the misc device, dynamic for now, and
> > reserve one when you get a bit closer to merging into mainline.
>
> Do you mean something like in the appended patch?
Yes, that looks good to me.
thanks,
greg k-h
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <greg@kroah.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Pavel Machek <pavel@ucw.cz>, Linux PM <linux-pm@osdl.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [linux-pm] [RFC/RFT][PATCH -mm 2/5] swsusp: userland interface (rev. 2)
Date: Thu, 5 Jan 2006 15:45:28 -0800 [thread overview]
Message-ID: <20060105234528.GA28365@kroah.com> (raw)
In-Reply-To: <200601060034.53707.rjw@sisk.pl>
On Fri, Jan 06, 2006 at 12:34:52AM +0100, Rafael J. Wysocki wrote:
> > Ok, then I'd recommend using the misc device, dynamic for now, and
> > reserve one when you get a bit closer to merging into mainline.
>
> Do you mean something like in the appended patch?
Yes, that looks good to me.
thanks,
greg k-h
next prev parent reply other threads:[~2006-01-05 23:45 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 [this message]
2006-01-05 23:45 ` 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
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=20060105234528.GA28365@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@osdl.org \
--cc=pavel@ucw.cz \
--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.