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]
Date:	Sun, 21 Nov 2010 15:53:41 -0500
From:	Eric Cooper <ecc@....edu>
To:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] add netdev led trigger

On Wed, Nov 17, 2010 at 08:09:19AM -0800, Greg KH wrote:
> Documentation/ABI is the correct place for it.

Should I just add descriptions of the additional attributes to the end
of the existing Documentation/ABI/testing/sysfs-class-led file?  If
so, how should I indicate that these attributes pertain only when the
ledtrig-netdev trigger is in use?

Or should I create a file specific to this trigger, and if so, what
should it be named?

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ