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

Date:	Wed, 22 Feb 2012 14:25:57 -0700
From:	Stephen Warren <swarren@...dia.com>
To:	Linus Walleij <linus.walleij@...aro.org>
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, Stephen Warren <swarren@...dia.com>
Subject: [PATCH V2 0/4] pinctrl: Rebased/extracted patches

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

 Documentation/pinctrl.txt       |   15 ++---
 drivers/pinctrl/core.c          |  131 +++++++++++++-------------------------
 drivers/pinctrl/core.h          |   11 ++--
 drivers/pinctrl/pinmux.c        |    2 +-
 include/linux/pinctrl/machine.h |    7 --
 5 files changed, 57 insertions(+), 109 deletions(-)

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