linux-kernel - RE: Question about cleaning up the LP5521/5523 LED driver

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: <A874F61F95741C4A9BA573A70FE3998F41EF52A7@DQHE02.ent.ti.com>
Date:	Mon, 17 Sep 2012 23:14:41 +0000
From:	"Kim, Milo" <Milo.Kim@...com>
To:	Linus Walleij <linus.walleij@...aro.org>
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

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

OK, thanks for your great help !

Best Regards,
Milo
--
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/