linux-kernel - Re: Freezer.h updated patch.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200610222227.45973.rjw@sisk.pl>
Date:	Sun, 22 Oct 2006 22:27:45 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Andrew Morton <akpm@...l.org>
Cc:	Nigel Cunningham <ncunningham@...uxmail.org>,
	LKML <linux-kernel@...r.kernel.org>, Pavel Machek <pavel@....cz>
Subject: Re: Freezer.h updated patch.

On Sunday, 22 October 2006 20:39, Andrew Morton wrote:
> On Sun, 22 Oct 2006 14:29:33 +0200
> "Rafael J. Wysocki" <rjw@...k.pl> wrote:
> 
> > Hi,
> > 
> > On Sunday, 22 October 2006 14:14, Nigel Cunningham wrote:
> > > Hi guys.
> > > 
> > > I missed a couple of "#include <freezer.h>"s in yesterdays patch;
> > > funnily enough the ones in kernel/power! Here's an updated version.
> > > 
> > > Rafael, did you still think the freezer.h contents should go into
> > > suspend.h?
> > 
> > Yes.
> > 
> 
> I think freezer.h is OK.  One 84-line file which does one thing is nice. 
> There's little advantage to putting this code into suspend.h along with a
> bunch of somewhat-unrelated stuff.

All of this stuff has one thing in common: it is only used for suspend
(to disk or to RAM) now.

> And it expresses the point that the freezer could be used for things other
> than suspend.  

Okay, then.  Let's take the patch as is.


-- 
You never change things by fighting the existing reality.
		R. Buckminster Fuller
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/