From: Greg KH <gregkh@suse.de>
To: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: [GIT PATCH] Driver Core patches for 2.6.18-rc1
Date: Wed, 12 Jul 2006 16:23:43 -0700 [thread overview]
Message-ID: <20060712232343.GA22672@kroah.com> (raw)
Here are some driver core patches and fixes for 2.6.18-rc1. They
contain the following changes:
- documentation fixes
- remove unused functions and symbols
All of these patches have been in the -mm tree for a while.
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-2.6.git/
or if master.kernel.org hasn't synced up yet:
master.kernel.org:/pub/scm/linux/kernel/git/gregkh/driver-2.6.git/
Patches will be sent as a follow-on to this message to lkml for people
to see.
thanks,
greg k-h
Documentation/feature-removal-schedule.txt | 8 ------
drivers/base/bus.c | 5 ++--
drivers/base/core.c | 30 +++++++++++------------
include/linux/ioport.h | 2 +-
include/linux/pm_legacy.h | 7 -----
kernel/power/pm.c | 37 ----------------------------
kernel/resource.c | 2 --
7 files changed, 19 insertions(+), 72 deletions(-)
---------------
Adrian Bunk:
Driver core: bus.c cleanups
remove kernel/power/pm.c:pm_unregister_all()
The scheduled unexport of insert_resource
Henrik Kretzschmar:
Driver core: kernel-doc in drivers/base/core.c corrections
Randy Dunlap:
Driver core: fix driver-core kernel-doc
next reply other threads:[~2006-07-12 23:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-12 23:23 Greg KH [this message]
2006-07-12 23:26 ` [PATCH 1/5] [PATCH] Driver core: fix driver-core kernel-doc Greg KH
2006-07-12 23:26 ` [PATCH 2/5] [PATCH] Driver core: kernel-doc in drivers/base/core.c corrections Greg KH
2006-07-12 23:26 ` [PATCH 3/5] [PATCH] Driver core: bus.c cleanups Greg KH
2006-07-12 23:26 ` [PATCH 4/5] [PATCH] remove kernel/power/pm.c:pm_unregister_all() Greg KH
2006-07-12 23:26 ` [PATCH 5/5] [PATCH] The scheduled unexport of insert_resource Greg KH
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=20060712232343.GA22672@kroah.com \
--to=gregkh@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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.