From: Greg KH <gregkh@suse.de>
To: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, kay.sievers@suse.de
Subject: [GIT PATCH] Driver Core fixe for 2.6.16-rc4
Date: Wed, 22 Feb 2006 09:43:39 -0800 [thread overview]
Message-ID: <20060222174339.GA11415@kroah.com> (raw)
Here is a single changeset, backing out the umount/mount uevent removal
from the kernel tree. It was my fault in the first place for thinking
that this event could be removed, as I was not aware the current version
of HAL depended on it so much.
Please pull from:
rsync://rsync.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/
The patch will be sent as a follow-up message for those that wish to see
it.
thanks,
greg k-h
Documentation/feature-removal-schedule.txt | 9 +++++++++
fs/super.c | 15 ++++++++++++++-
include/linux/kobject.h | 6 ++++--
lib/kobject_uevent.c | 4 ++++
4 files changed, 31 insertions(+), 3 deletions(-)
next reply other threads:[~2006-02-22 17:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-22 17:43 Greg KH [this message]
2006-02-22 17:44 ` [PATCH] Revert mount/umount uevent removal 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=20060222174339.GA11415@kroah.com \
--to=gregkh@suse.de \
--cc=akpm@osdl.org \
--cc=kay.sievers@suse.de \
--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