On Tue, Nov 22, 2016 at 9:08 AM, Bart Van Assche
<Bart.VanAssche@xxxxxxxxxxx> wrote:
> On 11/21/16 11:23, Shaun Tancheff wrote:
>> +/* -------------------------------------------------------------------------- */
>> +/* --ProcFS Support Routines------------------------------------------------- */
>> +/* -------------------------------------------------------------------------- */
>> +
>> +#if defined(CONFIG_PROC_FS)
>> +
>> +/**
>> + * struct zone_info_entry - Proc zone entry.
>> + * @zone: Zone Index
>> + * @info: Info (WP/Used).
>> + */
>> +struct zone_info_entry {
>> + u32 zone;
>> + u32 info;
>> +};
>> +
>> +/**
>> + * Startup writing to our proc entry
>> + */
>> +static void *proc_wp_start(struct seq_file *seqf, loff_t *pos)
>> +{
>> + struct zdm *znd = seqf->private;
>> +
>> + if (*pos == 0)
>> + znd->wp_proc_at = *pos;
>> + return &znd->wp_proc_at;
>> +}
>
> Hello Shaun,
>
> Does this mean that you are not aware that it is considered unacceptable
> for new drivers to create procfs entries?
I understood that it was frowned on.
I can move all but the 'status' to debugfs and move 'status' to sysfs
and reformat
the output as appropriate.... would that suffice?
> Bart.
--
dm-devel mailing list
dm-devel@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/dm-devel
