[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <d0a34f71-1b78-e387-c3a5-d771995a91f6@linux.ibm.com>
Date: Tue, 5 Nov 2019 22:31:09 +0530
From: Hari Bathini <hbathini@...ux.ibm.com>
To: Sourabh Jain <sourabhjain@...ux.ibm.com>, mpe@...erman.id.au
Cc: corbet@....net, mahesh@...ux.vnet.ibm.com,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
linuxppc-dev@...abs.org
Subject: Re: [PATCH v2 3/4] Documentation/ABI: mark /sys/kernel/fadump_* sysfs
files deprecated
On 05/11/19 2:24 PM, Sourabh Jain wrote:
>
>
> On 10/21/19 1:11 PM, Hari Bathini wrote:
>>
>>
>> On 18/10/19 6:35 PM, Sourabh Jain wrote:
>>> The /sys/kernel/fadump_* sysfs files are replicated under
>>
>> [...]
>>
>>> +Note: The following FADump sysfs files are deprecated.
>>> +
>>> + Deprecated Alternative
>>> + -------------------------------------------------------------------------------
>>> + /sys/kernel/fadump_enabled /sys/kernel/fadump/fadump_enabled
>>> + /sys/kernel/fadump_registered /sys/kernel/fadump/fadump_registered
>>> + /sys/kernel/fadump_release_mem /sys/kernel/fadump/fadump_release_mem
>>
>> /sys/kernel/fadump/* looks tidy instead of /sys/kernel/fadump/fadump_*
>> I mean, /sys/kernel/fadump/fadump_enabled => /sys/kernel/fadump/enabled and such..
>
>
>
> Could you please confirm whether you want to address the sysfs file path differently or
> actually changing the sysfs file name from fadump_enabled to enabled.
I meant, given the path "/sys/kernel/fadump/", the prefix fadump_ is redundant.
If there are no conventions that we should retain the same file name, I suggest
to drop the fadump_ prefix and just call them enabled, registered, etc..
- Hari
Powered by blists - more mailing lists