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] [day] [month] [year] [list]

Message-ID: <20101201195638.GE15294@elf.ucw.cz>
Date:	Wed, 1 Dec 2010 20:56:38 +0100
From:	Pavel Machek <pavel@....cz>
To:	linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org,
	gregkh@....ucw.cz
Subject: Re: [PATCH] add netdev led trigger

Hi!

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

Greg is official sysfs maintainer.

> 1. "0" and "1"

This should do the trick.

> 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?
									Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
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/