linux-kernel - [GIT PATCH] driver core patch against 2.6.26-rc4

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]

Message-ID: <20080530041528.GA13743@suse.de>
Date:	Thu, 29 May 2008 21:15:28 -0700
From:	Greg KH <gregkh@...e.de>
To:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Cc:	linux-kernel@...r.kernel.org,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	Kay Sievers <kay.sievers@...y.org>
Subject: [GIT PATCH] driver core patch against 2.6.26-rc4

Here is a single patch against your 2.6.26-git tree.

It was suggested by Stephen, as it will help with the linux-next merge
issues starting to happen as this api changes in anticipation for
2.6.27.  This patch merges a functional version of the dev_set_name()
function for other trees to be able to take adnd merge in changes that
help with the progression toward getting rid of the bus_id field and the
limitation of 20 characters for the name of struct device.

Please pull from:
	master.kernel.org:/pub/scm/linux/kernel/git/gregkh/driver-2.6.git/

The patch will be sent as a follow-on to this message to lkml for people
to see.

thanks,

greg k-h

------------

 drivers/base/core.c    |   15 +++++++++++++++
 include/linux/device.h |    3 +++
 2 files changed, 18 insertions(+), 0 deletions(-)

---------------

Stephen Rothwell (1):
      driver-core: prepare for 2.6.27 api change by adding dev_set_name

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