public inbox for linux-kernel@vger.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
Subject: [GIT PATCH] another driver core patch for .35
Date: Tue, 25 May 2010 15:15:46 -0700	[thread overview]
Message-ID: <20100525221546.GA29511@kroah.com> (raw)

Here's one more driver core patch for the .35 merge window.

It provides the ability for module-init-tools to know which modules to
load when a user asks for a device node that is not present in the
system yet by exporting the information in the modules.

It also moves some misc devices from a dynamic number to a static one as
they are getting popular on a lot of systems.

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

This patch has been in the linux-next and mm trees.

The patch will be sent as a follow-on to this message to lkml for people
to see, but it's already been sent there a number of times, so it's
nothing new.

thanks,

greg k-h

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

 Documentation/devices.txt        |    2 ++
 arch/x86/kernel/microcode_core.c |    1 +
 drivers/net/ppp_generic.c        |    4 ++--
 drivers/net/tun.c                |    1 +
 fs/autofs4/dev-ioctl.c           |    5 ++++-
 fs/btrfs/super.c                 |    5 ++++-
 fs/fuse/dev.c                    |    1 +
 include/linux/miscdevice.h       |    2 ++
 8 files changed, 17 insertions(+), 4 deletions(-)

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

Kay Sievers (1):
      driver core: add devname module aliases to allow module on-demand auto-loading


             reply	other threads:[~2010-05-25 22:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-25 22:15 Greg KH [this message]
2010-05-25 22:16 ` [PATCH 1/1] driver core: add devname module aliases to allow module on-demand auto-loading Greg Kroah-Hartman
2010-05-25 22:39   ` Randy Dunlap

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=20100525221546.GA29511@kroah.com \
    --to=gregkh@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox