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: <CACRpkdYQ8X7iwvHoecwYs1TZG_yP281FR-ZN7JCO=HUVp-05Ew@mail.gmail.com>
Date:	Mon, 17 Sep 2012 15:44:00 +0200
From:	Linus Walleij <linus.walleij@...aro.org>
To:	"Kim, Milo" <Milo.Kim@...com>
Cc:	Bryan Wu <bryan.wu@...onical.com>,
	"linux-leds@...r.kernel.org" <linux-leds@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: Question about cleaning up the LP5521/5523 LED driver

On Mon, Sep 17, 2012 at 1:28 PM, Kim, Milo <Milo.Kim@...com> wrote:

> Should I keep the sysfs layout of LP5521 and LP5523?
> When we change the device attributes, do we have to consider the backward compatibility?

The ABI is a contract so basically yes, you need real good reasons
(like security concerns) to change the ABI.

That said, the lm3533 is the only LED driver that has actually documented
its ABI: Documentation/ABI/testing/sysfs-class-led-driver-lm3533

Yours,
Linus Walleij
--
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