From: Greg KH <greg@kroah.com>
To: torvalds@osdl.org, akpm@osdl.org
Cc: linux-kernel@vger.kernel.org
Subject: [BK PATCH] Driver Core patches for 2.6.10-rc1
Date: Mon, 1 Nov 2004 13:54:18 -0800 [thread overview]
Message-ID: <20041101215418.GA16500@kroah.com> (raw)
Hi,
Here are some driver core patches for 2.6.10-rc1. The majority of them
have all been in the -mm tree for a while. They contain:
- bugfix for the hotplug calls that was breaking all firmware
downloads.
- sysfs backing patches. Finally Maneesh can rest...
- add a "driver" symlink in devices to make it easier to
determine what driver is bound to a specific device.
- other bugfixes.
Please pull from:
bk://kernel.bkbits.net/gregkh/linux/driver-2.6
thanks,
greg k-h
p.s. I'll send these as patches in response to this email to lkml for
those who want to see them.
drivers/base/bus.c | 61 +++---
drivers/base/power/main.c | 11 -
drivers/base/power/power.h | 5
drivers/base/power/resume.c | 16 +
drivers/base/power/suspend.c | 44 ++--
drivers/input/input.c | 2
drivers/input/serio/serio.c | 7
drivers/pnp/pnpbios/core.c | 2
drivers/s390/crypto/z90main.c | 1
fs/sysfs/bin.c | 60 ++----
fs/sysfs/dir.c | 379 +++++++++++++++++++++++++++++++++++------
fs/sysfs/file.c | 98 +++++-----
fs/sysfs/group.c | 4
fs/sysfs/inode.c | 102 ++++++++---
fs/sysfs/mount.c | 12 +
fs/sysfs/symlink.c | 65 ++++---
fs/sysfs/sysfs.h | 81 ++++++++
include/linux/device.h | 4
include/linux/kmod.h | 4
include/linux/kobject_uevent.h | 5
include/linux/sysfs.h | 19 ++
kernel/cpu.c | 1
kernel/kmod.c | 23 --
kernel/sysctl.c | 2
lib/kobject_uevent.c | 48 +++--
25 files changed, 742 insertions(+), 314 deletions(-)
-----
Dmitry Torokhov:
o Driver core: add driver symlink to device
o Driver core: add driver_probe_device
o Driver core: export device_attach
Kay Sievers:
o take me home, hotplug_path[]
o kobject: fix hotplug bug with seqnum
Maneesh Soni:
o sysfs backing store: stop pinning dentries/inodes for leaf entries
o sysfs backing store: use sysfs_dirent based tree in dir file operations
o sysfs backing store: use sysfs_dirent based tree in file removal
o sysfs backing store - add sysfs_direct structure
o fix oops with firmware loading
o sysfs backing store - prepare sysfs_file_operations helpers
Paul Mackerras:
o Fix deadlocks on dpm_sem
Simon Derr:
o Possible race in sysfs_read_file() and sysfs_write_file()
o Fix race in sysfs_read_file() and sysfs_write_file()
next reply other threads:[~2004-11-01 23:01 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-01 21:54 Greg KH [this message]
2004-11-01 21:57 ` [PATCH] " Greg KH
2004-11-01 21:57 ` Greg KH
2004-11-01 21:57 ` Greg KH
2004-11-01 21:57 ` Greg KH
2004-11-01 21:57 ` Greg KH
2004-11-01 21:57 ` Greg KH
2004-11-01 21:57 ` Greg KH
2004-11-01 21:57 ` Greg KH
2004-11-01 21:57 ` Greg KH
2004-11-01 21:57 ` Greg KH
2004-11-01 21:57 ` Greg KH
2004-11-01 21:57 ` Greg KH
2004-11-01 21:57 ` Greg KH
2004-11-01 21:57 ` Greg KH
2004-11-02 22:32 ` Russell King
2004-11-07 15:28 ` Russell King
2004-11-10 1:37 ` Greg KH
2004-11-10 2:57 ` Paul Mackerras
2004-11-10 8:36 ` Russell King
2004-11-10 21:36 ` Paul Mackerras
2004-11-11 0:00 ` Nigel Cunningham
2004-11-11 20:52 ` Russell King
2004-11-12 0:28 ` Greg KH
2004-11-01 23:44 ` Pozsar Balazs
-- strict thread matches above, loose matches on Subject: below --
2004-10-22 23:09 [BK PATCH] " 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=20041101215418.GA16500@kroah.com \
--to=greg@kroah.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome