linux-kernel - [PATCH 0/8] lp8727

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

Message-ID: <A874F61F95741C4A9BA573A70FE3998F41EF1C6B@DQHE02.ent.ti.com>
Date:	Thu, 30 Aug 2012 11:37:16 +0000
From:	"Kim, Milo" <Milo.Kim@...com>
To:	Anton Vorontsov <cbouatmailru@...il.com>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	David Woodhouse <dwmw2@...radead.org>,
	Anton Vorontsov <anton.vorontsov@...aro.org>
Subject: [PATCH 0/8] lp8727_charger: cleanup code

LP8727 driver should be patched for several reasons.

(a) Need to clean up _probe()/_remove()
(b) Not secure code when the platform data is NULL
(c) Interrupt handling
    Two threads are running for handling one IRQ.
    One is for the IRQ pin, the other is used for delayed processing.
    This is unusual and can be enhanced.
(d) Misuse of mutex code
(e) Lots of definitions should be fixed
(f) Others..

Bunch of code patches are as below.

[PATCH 1/8] lp8727_charger: use devm_kzalloc() rather than
 kzalloc()/kfree()
[PATCH 2/8] lp8727_charger: cleanup _probe() and _remove()
[PATCH 3/8] lp8727_charger: fix buggy code when the platform data is
 NULL
[PATCH 4/8] lp8727_charger: cleanup the interrupt handler code
[PATCH 5/8] lp8727_charger: move the mutex code
[PATCH 6/8] lp8727_charger: fix code for getting battery temperature
[PATCH 7/8] lp8727_charger: cleanup definitions
[PATCH 8/8] lp8727_charger: make cosmetic code

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/