linux-kernel - Re: [PATCH v2 001/001] gpio: AMD CS5535/CS5536 GPIO 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] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 01 Jun 2009 21:02:52 -0600
From:	Jordan Crouse <jordan@...micpenguin.net>
To:	Andres Salomon <dilinger@...labora.co.uk>
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	Tobias_Mueller@...m.info, david-b@...bell.net,
	gardner.ben@...il.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 001/001] gpio: AMD CS5535/CS5536 GPIO driver

Andres Salomon wrote:
> On Mon, 1 Jun 2009 16:54:57 -0700
> Andrew Morton <akpm@...ux-foundation.org> wrote:
> [...]
>> Back in February, Andres sent out a patch "cs553x-gpio: add AMD
>> CS5535/CS5536 GPIO driver support".  AFACIT that patch does the same
>> thing that this one does, but differently.  IIRC it had a great string
>> of weird-Kconfig-related build errors and I eventually dropped it.
>>
>> What's the story here?
>>
>> Thanks.
> 
> My story is that I've since switched employers twice since Feb, and will
> be resubmitting the patch now that sanity has returned to my life.
> I'm planning to get to it within the next week.
> 
> As far as Tobias's driver, one major difference between our drivers is
> that mine doesn't grab the entire PCI device.  This is because other
> drivers (ie, the MFGPT driver) will want to share the PCI device.

Also SMBUS. In fact, they *must* share the PCI device if they all want 
to play well together, so that alone would probably push us toward 
Andre's patch, once it gets clean.

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