From: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
To: Alan Cox <alan@redhat.com>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
torvalds@osdl.org
Subject: Re: PATCH: straighten out the IDE layer locking and add hotplug
Date: Mon, 16 Aug 2004 23:43:35 +0200 [thread overview]
Message-ID: <200408162343.35588.bzolnier@elka.pw.edu.pl> (raw)
In-Reply-To: <20040815151346.GA13761@devserv.devel.redhat.com>
> +/**
> + * ide_hwif_restore - restore hwif to template
> + * @hwif: hwif to update
> + * @tmp_hwif: template
> + *
> + * Restore hwif to a default state by copying most settngs
it restores hwif to previous state not the default one
> +/**
> + * ide_add_generic_settings - generic /proc settings
> + * @drive: drive being configured
> + *
> + * Add the generic parts of the system settings to the /proc files
> + * for this IDE device. The caller must not be holding the settings_sem
> + * .lock
> + */
ide settings are not limited to /proc, remember about ioctls
> +/**
> + * system_bus_clock - clock guess
> + *
> + * External version of the bus clock guess used by old old IDE drivers
old old?
> +/**
> + * ata_attach - attach an ATA/ATAPI device
> + * @drive: drive to attach
> + *
> + * Takes a drive that is as yet not assigned to any midlayer IDE
> + * module and figures out which driver would like to own it. If
drive maybe assinged to midlayer ide-default driver
> + * nobody claims the driver then it is automatically attached
the drive
> +/**
> + * ide_unregister_subdriver - disconnect drive from driver
> + * @drive: drive to unplug
> + *
> + * Disconnect a drive from the driver it was attached to and then
> + * clean up the various proc files and other objects attached to it.
> + * Takes ide_sem, ide_lock, and drive_lock. Caller must hold none of
> + * the locks.
> + *
> + * No locking versus subdriver unload because we are moving to the
> + * default driver anyway. Wants double checking.
yep, locking needs checking (removing hwif vs removing driver)
> +/**
> + * ide_register_driver - new driver loaded
> + * @driver: the IDE driver module
driver doesn't have to be a module
IDE device driver
> +/**
> + * ide_unregister_driver - IDE module unload
> + * @driver: IDE driver module
> + *
> + * Unload a driver module and reattach any devices to whatever
it doesn't unload given IDE device driver
next prev parent reply other threads:[~2004-08-16 22:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-15 15:13 Alan Cox
2004-08-16 17:23 ` Bartlomiej Zolnierkiewicz
2004-08-16 17:36 ` Alan Cox
2004-08-16 22:29 ` Bartlomiej Zolnierkiewicz
2004-08-16 21:43 ` Bartlomiej Zolnierkiewicz [this message]
2004-08-17 13:12 ` Bartlomiej Zolnierkiewicz
2004-08-17 14:05 ` Alan Cox
2004-08-17 14:30 ` Bartlomiej Zolnierkiewicz
2004-08-17 14:46 ` Alan Cox
2004-08-17 15:05 ` Bartlomiej Zolnierkiewicz
2004-08-17 15:33 ` Alan Cox
2004-08-17 14:40 ` Bartlomiej Zolnierkiewicz
2004-08-17 14:12 ` Bartlomiej Zolnierkiewicz
2004-08-17 14:18 ` Alan Cox
2004-08-17 14:35 ` Bartlomiej Zolnierkiewicz
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=200408162343.35588.bzolnier@elka.pw.edu.pl \
--to=b.zolnierkiewicz@elka.pw.edu.pl \
--cc=alan@redhat.com \
--cc=linux-ide@vger.kernel.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
all inboxes | Powered by JetHome®