linux-kernel - Re: [PATCH] add netdev led trigger

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20101130232204.GF21496@localhost>
Date:	Tue, 30 Nov 2010 18:22:04 -0500
From:	Eric Cooper <ecc@....edu>
To:	Pavel Machek <pavel@....cz>
Cc:	linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org
Subject: Re: [PATCH] add netdev led trigger

> Please be consistent with rest of kernel...

There seem to be several ways this is done in existing sysfs drivers,
and most aren't documented yet in Documentation/ABI.

1. "0" and "1"
2. "enable" and "disable"
3. "enabled" and "disabled"
4. "enable" and "disable" when writing, but "enabled" and "disabled"
    when read back

Some require trailing "\n", others make it optional.

Which is the One True Way?

-- 
Eric Cooper             e c c @ c m u . e d u
--
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/