linux-kernel - Re: [PATCH v3] lpc_ich: fix gpio base and control offsets

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CACRpkdYV3KGz45Ko1n-QJ6VQ4Y8SAb3zd87AvfpP1TSUAh=FsQ@mail.gmail.com>
Date:	Mon, 28 Jan 2013 11:11:49 +0100
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Samuel Ortiz <sameo@...ux.intel.com>
Cc:	Aaron Sierra <asierra@...-inc.com>,
	Paul Bolle <pebolle@...cali.nl>,
	Peter Hurley <peter@...leysoftware.com>,
	Agócs Pál <agocs.pal.86@...il.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3] lpc_ich: fix gpio base and control offsets

On Fri, Jan 25, 2013 at 5:48 PM, Samuel Ortiz <sameo@...ux.intel.com> wrote:
> On Fri, Jan 25, 2013 at 10:47:45AM +0100, Linus Walleij wrote:

>> So where is this id->driver_data which is just assigned to
>> priv->chipset coming from again? ACPI something?
>
> It comes from the static PCI table the driver defines itself. It allows you to
> pass meta data associated to a specific PCI ID.

OK cool, I think we can conclude that this patch is fine after the
boot tests and all:
Acked-by: Linus Walleij <linus.walleij@...aro.org>

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/