From: Pavel Machek <pavel@ucw.cz>
To: Adrian Bunk <bunk@stusta.de>
Cc: Andrew Morton <akpm@osdl.org>, "Rafael J. Wysocki" <rjw@sisk.pl>,
linux-kernel@vger.kernel.org, linux-pm@osdl.org
Subject: Re: [RFC: -mm patch] swsusp: make some code static
Date: Thu, 12 Jan 2006 16:29:35 +0100 [thread overview]
Message-ID: <20060112152935.GD9752@elf.ucw.cz> (raw)
In-Reply-To: <20060112104812.GR29663@stusta.de>
On Čt 12-01-06 11:48:12, Adrian Bunk wrote:
> On Wed, Jan 11, 2006 at 04:21:35AM -0800, Andrew Morton wrote:
> >...
> > Changes since 2.6.15-mm2:
> >...
> > +swsusp-low-level-interface-rev-2.patch
> >...
> > swsusp updates
> >...
>
> After this patch, we can make some code static.
>
>
> Signed-off-by: Adrian Bunk <bunk@stusta.de>
Rafael should comment here. It is okay, but Rafael has some patches in
the queue, and it would be better if there were to clashes.
Pavel
--
Thanks, Sharp!
next prev parent reply other threads:[~2006-01-12 15:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060111042135.24faf878.akpm@osdl.org>
2006-01-12 10:48 ` [RFC: -mm patch] swsusp: make some code static Adrian Bunk
2006-01-12 15:29 ` Pavel Machek [this message]
2006-01-12 16:18 ` Rafael J. Wysocki
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=20060112152935.GD9752@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox