linux-kernel - Re: [PATCH 0/5] ab8500 gpadc fixes

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]

Date:	Mon, 14 Mar 2011 11:26:51 +0100
From:	Samuel Ortiz <sameo@...ux.intel.com>
To:	Linus Walleij <linus.walleij@...ricsson.com>
Cc:	linux-kernel@...r.kernel.org, Lee Jones <lee.jones@...aro.org>,
	Linus Walleij <linus.walleij@...aro.org>,
	Daniel Willerud <daniel.willerud@...ricsson.com>,
	Mattias Wallin <mattias.wallin@...ricsson.com>,
	Karl Komierowski <karl.komierowski@...ricsson.com>,
	Johan Palsson <johan.palsson@...ricsson.com>,
	Arun Murthy <arun.murthy@...ricsson.com>
Subject: Re: [PATCH 0/5] ab8500 gpadc fixes

Hi Linus,

On Mon, Mar 14, 2011 at 11:21:10AM +0100, Samuel Ortiz wrote:
> Hi Linus,
> 
> On Sat, Mar 05, 2011 at 11:45:35AM +0100, Linus Walleij wrote:
> > From: Linus Walleij <linus.walleij@...aro.org>
> > 
> > I have broken Daniels patch apart, fixed the GPADC fetch
> > interface as agreed with Sam, added the proper authorship of
> > the calibration patch to Johan and also put a new patch from
> > Karl Komierowski to fix proper charging ADC on top.
> Thanks a lot, all 5 patches applied now.
One more thing: I'd like to see the ab8500-gpadc.h header be renamed to
gpadc.h now that it's under the ab8500 directory. No rush, but something I'd
like to get from your next patchsets. Thanks in advance.

Cheers,
Samuel.

-- 
Intel Open Source Technology Centre
http://oss.intel.com/
--
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/