From: Nigel Cunningham <ncunningham@cyclades.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Andrew Morton <akpm@digeo.com>, Pavel Machek <pavel@ucw.cz>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Add missing refrigerator calls
Date: Wed, 16 Mar 2005 09:53:43 +1100 [thread overview]
Message-ID: <1110927223.6454.148.camel@desktop.cunningham.myip.net.au> (raw)
In-Reply-To: <1110925639.9818.80.camel@pegasus>
Hi.
On Wed, 2005-03-16 at 09:27, Marcel Holtmann wrote:
> Hi Nigel,
>
> > There are a number of threads that currently have no refrigerator
> > handling in Linus' tree. This patch addresses part of that issue. The
> > remainder will be addressed in other patches, following soon.
> >
> > Signed-off-by: Nigel Cunningham <ncunningham@cyclades.com>
>
> I am fine with the net/bluetooth/rfcomm/ part, but what about the bnep/
> and cmtp/ and hidp/ part of the Bluetooth subsystem? Do we need this
> there, too?
I see... someone has added PF_NOFREEZE to all your drivers, so my
fragment is redundant. NO_FREEZE is fine in my mind - I would be seeking
to make all network driver threads NO_FREEZE in a while anyway, to allow
suspending over a network.
I'll double check the other fragments too, just in case the same thing
has happened there.
Nigel
--
Nigel Cunningham
Software Engineer, Canberra, Australia
http://www.cyclades.com
Bus: +61 (2) 6291 9554; Hme: +61 (2) 6292 8028; Mob: +61 (417) 100 574
Maintainer of Suspend2 Kernel Patches http://suspend2.net
next prev parent reply other threads:[~2005-03-15 22:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-15 22:12 Nigel Cunningham
2005-03-15 22:27 ` Marcel Holtmann
2005-03-15 22:53 ` Nigel Cunningham [this message]
2005-03-15 23:14 ` [PATCH] (Revised) " Nigel Cunningham
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=1110927223.6454.148.camel@desktop.cunningham.myip.net.au \
--to=ncunningham@cyclades.com \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--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
all inboxes | Powered by JetHome®