From: Patrick Mochel <mochel@osdl.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: Nigel Cunningham <ncunningham@clear.net.nz>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: SWSUSP Discontiguous pagedir patch
Date: Mon, 10 Mar 2003 10:51:21 -0600 (CST) [thread overview]
Message-ID: <Pine.LNX.4.33.0303101049290.1002-100000@localhost.localdomain> (raw)
In-Reply-To: <20030307203650.GB2447@elf.ucw.cz>
> > The cumulative patch is here:
> >
> > http://kernel.org/pub/linux/kernel/people/mochel/power/pm-2.5.64.diff.gz
>
> Hmm, I am not sure if drivers/power is the right place for stuff like
> fridge.c. That might be usefull for other stuff, too.
That's fine. If it proves useful for other things, we can move it.
> I do not think placing swsusp.h in drivers/power/swsusp is right. It
> should be in include/linux or include/linux/power.
That header is only for the shared functions between
drivers/power/swsusp/*.c. There's no need to export it to everyone.
Under the new model, nothing would call swsusp directly. It would call the
model's functions, which would delegate the call to the user-specified
handler for the action.
-pat
next prev parent reply other threads:[~2003-03-10 17:05 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1045784829.3821.10.camel@laptop-linux.cunninghams>
[not found] ` <20030223223757.GA120@elf.ucw.cz>
[not found] ` <1046136752.1784.15.camel@laptop-linux.cunninghams>
[not found] ` <20030227132024.GB27084@atrey.karlin.mff.cuni.cz>
2003-02-27 18:42 ` SWSUSP Discontiguous pagedirs Nigel Cunningham
2003-03-01 4:22 ` SWSUSP Discontiguous pagedir patch Nigel Cunningham
2003-03-02 23:55 ` Patrick Mochel
2003-03-03 2:06 ` Nigel Cunningham
2003-03-03 2:31 ` Nigel Cunningham
2003-03-03 12:30 ` Pavel Machek
2003-03-04 20:36 ` Patrick Mochel
2003-03-05 20:50 ` Pavel Machek
2003-03-05 21:52 ` Linux vs Windows temperature anomaly Jonathan Lundell
2003-03-05 23:11 ` Herman Oosthuysen
2003-03-05 23:38 ` Con Kolivas
2003-03-05 23:50 ` Russell King
2003-03-06 0:29 ` Ed Sweetman
2003-03-06 0:47 ` Trever L. Adams
2003-03-06 9:45 ` Russell King
2003-03-06 1:58 ` Jonathan Lundell
2003-03-06 7:18 ` Corvus Corax
2003-03-06 7:57 ` Ed Sweetman
2003-03-06 8:18 ` Corvus Corax
2003-03-06 8:58 ` Ed Sweetman
2003-03-06 15:41 ` Jesse Pollard
2003-03-06 14:27 ` Jesse Pollard
2003-03-06 2:57 ` David Rees
2003-03-06 6:12 ` Matthias Schniedermeyer
2003-03-06 16:07 ` Jonathan Lundell
2003-03-07 0:40 ` Horst von Brand
2003-03-05 18:02 ` SWSUSP Discontiguous pagedir patch Pavel Machek
2003-03-07 17:14 ` Patrick Mochel
2003-03-07 20:27 ` Pavel Machek
2003-03-09 19:39 ` Benjamin Herrenschmidt
2003-03-09 20:12 ` Pavel Machek
2003-03-10 16:49 ` Patrick Mochel
2003-03-10 19:23 ` Pavel Machek
2003-03-10 19:05 ` Patrick Mochel
2003-03-10 22:17 ` Nigel Cunningham
2003-03-10 23:20 ` Pavel Machek
2003-03-07 20:36 ` Pavel Machek
2003-03-10 16:51 ` Patrick Mochel [this message]
2003-03-10 19:12 ` Pavel Machek
2003-03-10 18:59 ` Patrick Mochel
2003-03-07 20:41 ` 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=Pine.LNX.4.33.0303101049290.1002-100000@localhost.localdomain \
--to=mochel@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ncunningham@clear.net.nz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).