linux-kernel - Re: [patch] suspend/resume debugging: device filter

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: <1169724526.1316.8.camel@nigel.suspend2.net>
Date:	Thu, 25 Jan 2007 22:28:46 +1100
From:	Nigel Cunningham <nigel@...el.suspend2.net>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Andrew Morton <akpm@...l.org>, linux-kernel@...r.kernel.org,
	Pavel Machek <pavel@....cz>,
	Linus Torvalds <torvalds@...l.org>, Greg KH <gregkh@...e.de>
Subject: Re: [patch] suspend/resume debugging: device filter

Hi.

On Thu, 2007-01-25 at 12:05 +0100, Ingo Molnar wrote:
> it might be better to do this centrally in sysfs, via a per-device 
> attribute, to individually enable suspend and resume on a per device 
> basis, but my sysfs-fu is not strong enough for that now ;-)

Yeah. I was thinking recently of doing a per-device attribute, but like
so many things at the moment, getting around to it is a little bit of a
problem.

> Signed-off-by: Ingo Molnar <mingo@...e.hu>
> ---
>  drivers/base/power/resume.c  |    6 ++++
>  drivers/base/power/suspend.c |    3 +-
>  include/linux/resume-trace.h |    6 ++++
>  kernel/power/main.c          |   58 +++++++++++++++++++++++++++++++++++++++++++

Should the sysfs stuff (not just this) be in kernel/power/main.c? I
wonder if it would be better put in drivers/base?

Regards,

Nigel

-
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/