From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: nigel@suspend2.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Suspend2][ 0/7] Proc file support
Date: Tue, 27 Jun 2006 23:00:25 +0200 [thread overview]
Message-ID: <200606272300.25933.rjw@sisk.pl> (raw)
In-Reply-To: <200606270850.47419.nigel@suspend2.net>
On Tuesday 27 June 2006 00:50, Nigel Cunningham wrote:
> Hi.
>
> On Tuesday 27 June 2006 06:07, Rafael J. Wysocki wrote:
> > On Monday 26 June 2006 18:47, Nigel Cunningham wrote:
> > > Generic routines for implementing the /proc/suspend2 files that allow
> > > the user to configure and tune the subsystem according to their needs.
> >
> > All of the following patches seem to modify the same file:
> > kernel/power/proc.c I'd prefer if these changes were all done in one patch.
> >
> > Rafael
>
> I've done this with all the new files, so that each part of the file can be
> considered without suffering from overload.
Well, different parts of the same file tend to depend on each other and it's
sometimes hard to follow the dependencies if they are in different patches.
Rafael
prev parent reply other threads:[~2006-06-27 21:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-26 16:47 Nigel Cunningham
2006-06-26 16:47 ` [Suspend2][ 1/7] [Suspend2] Proc.c header Nigel Cunningham
2006-06-26 16:47 ` [Suspend2][ 2/7] [Suspend2] Read a proc file entry Nigel Cunningham
2006-06-26 16:47 ` [Suspend2][ 3/7] [Suspend2] Proc write routine Nigel Cunningham
2006-06-26 16:47 ` [Suspend2][ 4/7] [Suspend2] Basic (do_suspend/do_resume) entries Nigel Cunningham
2006-06-26 16:47 ` [Suspend2][ 5/7] [Suspend2] Initialise the proc directories & basic entries Nigel Cunningham
2006-06-26 16:47 ` [Suspend2][ 6/7] [Suspend2] Register and remove proc file functions Nigel Cunningham
2006-06-26 16:47 ` [Suspend2][ 7/7] [Suspend2] Suspend2 proc.h Nigel Cunningham
2006-06-26 20:07 ` [Suspend2][ 0/7] Proc file support Rafael J. Wysocki
2006-06-26 22:50 ` Nigel Cunningham
2006-06-27 21:00 ` Rafael J. Wysocki [this message]
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=200606272300.25933.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=nigel@suspend2.net \
/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
all inboxes | Powered by JetHome®