[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <x2sd6200be21004232154i4738d938vf57ade1b702cf404@mail.gmail.com>
Date: Fri, 23 Apr 2010 21:54:29 -0700
From: Arve Hjønnevåg <arve@...roid.com>
To: Randy Dunlap <randy.dunlap@...cle.com>
Cc: linux-pm@...ts.linux-foundation.org, linux-kernel@...r.kernel.org,
Pavel Machek <pavel@....cz>, "Rafael J. Wysocki" <rjw@...k.pl>,
Len Brown <len.brown@...el.com>
Subject: Re: [PATCH 5/9] PM: suspend_block: Add debugfs file
2010/4/23 Randy Dunlap <randy.dunlap@...cle.com>:
> On 04/23/10 20:23, Arve Hjønnevåg wrote:
>> 2010/4/23 Randy Dunlap <randy.dunlap@...cle.com>:
>>> On Thu, 22 Apr 2010 18:08:54 -0700 Arve Hjønnevåg wrote:
>>>
>>>> Report active and inactive suspend blockers in
>>>> /sys/kernel/debug/suspend_blockers.
>>>
>>>
>>> This looks more like user interface information than it does debug information.
>>> If that's correct, it shouldn't be in debugfs.
>>
>> Where should it be? It is not allowed in sysfs, and procfs does not
>> appear to be open to new files.
>
> Why is it not allowed in sysfs? due to more than one value per file
Yes.
> or something else?
>
> I don't think that procfs is closed to new files, but you may have to
> justify why it should be used.
>
I used procfs in the original version and there were a lot of
objections to this, so I moved it to debugfs.
--
Arve Hjønnevåg
--
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/
Powered by blists - more mailing lists