All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Kay Sievers <kay.sievers@vrfy.org>
Subject: [GIT PATCH] driver core patch against 2.6.26-rc4
Date: Thu, 29 May 2008 21:15:28 -0700	[thread overview]
Message-ID: <20080530041528.GA13743@suse.de> (raw)

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


             reply	other threads:[~2008-05-30  4:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-30  4:15 Greg KH [this message]
2008-05-30  4:16 ` [PATCH 1/1] driver-core: prepare for 2.6.27 api change by adding dev_set_name Greg Kroah-Hartman
2008-05-30  4:16 ` Greg Kroah-Hartman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080530041528.GA13743@suse.de \
    --to=gregkh@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.