linux-kernel - Re: [PATCH V2 0/4] pinctrl: Rebased/extracted patches

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: <CACRpkdZPNGTG8HvWk4cf+DdJvEpr6o38L6mdvt4v2mEV0mvCzw@mail.gmail.com>
Date:	Fri, 24 Feb 2012 06:33:17 +0100
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Stephen Warren <swarren@...dia.com>
Cc:	Linus Walleij <linus.walleij@...ricsson.com>, B29396@...escale.com,
	s.hauer@...gutronix.de, dongas86@...il.com, shawn.guo@...aro.org,
	thomas.abraham@...aro.org, tony@...mide.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH V2 0/4] pinctrl: Rebased/extracted patches

On Wed, Feb 22, 2012 at 10:25 PM, Stephen Warren <swarren@...dia.com> wrote:

> The first 3 patches were previously ack'd but weren't applied due to earlier
> patches in the original series not having been applied. These rebased versions
> can be applied directly on top of the pinctrl for-next branch.
>
> The last patch is the conceptually ack'd portion of the larger locking rework
> patch, extracted on its own for commit.
>
> Stephen Warren (4):
>  pinctrl: Disallow map table entries with NULL dev_name field
>  pinctrl: Use dev_*() instead of pr_*(), add some msgs, minor cleanups
>  pinctrl: Allocate sizeof(*p) instead of sizeof(struct foo)
>  pinctrl: Remove pin and hogs locks from struct pinctrl_dev

Thanks a ton Stephen, all patches applied and pushed to for-next.

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/