From: Tejun Heo <tj@kernel.org>
To: axboe@kernel.dk, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org, kay.sievers@vrfy.org, jack@suse.cz,
James.Bottomley@HansenPartnership.com
Cc: Tejun Heo <tj@kernel.org>
Subject: [PATCH 1/7] block: kill genhd_media_change_notify()
Date: Mon, 1 Nov 2010 19:44:35 +0100 [thread overview]
Message-ID: <1288637081-5183-2-git-send-email-tj@kernel.org> (raw)
In-Reply-To: <1288637081-5183-1-git-send-email-tj@kernel.org>
There's no user of the facility. Kill it.
Signed-off-by: Tejun Heo <tj@kernel.org>
---
block/genhd.c | 25 -------------------------
include/linux/genhd.h | 1 -
2 files changed, 0 insertions(+), 26 deletions(-)
diff --git a/block/genhd.c b/block/genhd.c
index 5fa2b44..0905ab2 100644
--- a/block/genhd.c
+++ b/block/genhd.c
@@ -1110,29 +1110,6 @@ static int __init proc_genhd_init(void)
module_init(proc_genhd_init);
#endif /* CONFIG_PROC_FS */
-static void media_change_notify_thread(struct work_struct *work)
-{
- struct gendisk *gd = container_of(work, struct gendisk, async_notify);
- char event[] = "MEDIA_CHANGE=1";
- char *envp[] = { event, NULL };
-
- /*
- * set enviroment vars to indicate which event this is for
- * so that user space will know to go check the media status.
- */
- kobject_uevent_env(&disk_to_dev(gd)->kobj, KOBJ_CHANGE, envp);
- put_device(gd->driverfs_dev);
-}
-
-#if 0
-void genhd_media_change_notify(struct gendisk *disk)
-{
- get_device(disk->driverfs_dev);
- schedule_work(&disk->async_notify);
-}
-EXPORT_SYMBOL_GPL(genhd_media_change_notify);
-#endif /* 0 */
-
dev_t blk_lookup_devt(const char *name, int partno)
{
dev_t devt = MKDEV(0, 0);
@@ -1198,8 +1175,6 @@ struct gendisk *alloc_disk_node(int minors, int node_id)
disk_to_dev(disk)->class = &block_class;
disk_to_dev(disk)->type = &disk_type;
device_initialize(disk_to_dev(disk));
- INIT_WORK(&disk->async_notify,
- media_change_notify_thread);
}
return disk;
}
diff --git a/include/linux/genhd.h b/include/linux/genhd.h
index 7a7b9c1..5e4e692 100644
--- a/include/linux/genhd.h
+++ b/include/linux/genhd.h
@@ -173,7 +173,6 @@ struct gendisk {
struct timer_rand_state *random;
atomic_t sync_io; /* RAID */
- struct work_struct async_notify;
#ifdef CONFIG_BLK_DEV_INTEGRITY
struct blk_integrity *integrity;
#endif
--
1.7.1
next prev parent reply other threads:[~2010-11-01 18:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-01 18:44 [PATCHSET RFC] block/SCSI: implement in-kernel disk event handling Tejun Heo
2010-11-01 18:44 ` Tejun Heo [this message]
2010-11-01 18:44 ` [PATCH 2/7] block: move register_disk() and del_gendisk() to block/genhd.c Tejun Heo
2010-11-01 18:44 ` [PATCH 3/7] implement in-kernel gendisk events handling Tejun Heo
2010-11-01 18:44 ` [PATCH 4/7] cdrom: add ->check_events() support Tejun Heo
2010-11-01 18:44 ` [PATCH 5/7] scsi: replace sr_test_unit_ready() with scsi_test_unit_ready() Tejun Heo
2010-11-01 18:44 ` [PATCH 6/7] sr: implement sr_check_events() Tejun Heo
2010-11-01 18:44 ` [PATCH 7/7] sd: implement sd_check_events() Tejun Heo
2010-11-04 17:07 ` [PATCHSET RFC] block/SCSI: implement in-kernel disk event handling Douglas Gilbert
2010-11-04 18:37 ` Mike Anderson
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=1288637081-5183-2-git-send-email-tj@kernel.org \
--to=tj@kernel.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=axboe@kernel.dk \
--cc=jack@suse.cz \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.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.