From: Randy Dunlap <randy_d_dunlap@linux.intel.com>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: linux-scsi@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: [PATCH] shutdown processing
Date: Thu, 16 Feb 2006 10:40:07 -0800 [thread overview]
Message-ID: <20060216104007.67cf613f.randy_d_dunlap@linux.intel.com> (raw)
In-Reply-To: <43F43EB9.40406@s5r6.in-berlin.de>
On Thu, 16 Feb 2006 09:58:33 +0100
Stefan Richter <stefanr@s5r6.in-berlin.de> wrote:
> Randy Dunlap wrote:
> > From: Randy Dunlap <randy_d_dunlap@linux.intel.com>
> >
> > Add ability for SCSI drivers to invoke a shutdown method.
> > This allows drivers to make drives safe for shutdown/poweroff,
> > for example. Some drives need this to prevent possible problems.
> >
> > Signed-off-by: Randy Dunlap <randy_d_dunlap@linux.intel.com>
>
> Why are you calling these from SCSI? Wouldn't ahci_pci_driver.remove()
> and piix_pci_driver.remove() be a proper place to perform what you are
> doing in ata_device_shutdown?
Mostly to have the scsi_device pointers available.
I'll try your suggestion.
> [...]
> > EXPORT_SYMBOL_GPL(ata_device_suspend);
> > EXPORT_SYMBOL_GPL(ata_device_resume);
> > +EXPORT_SYMBOL_GPL(ata_device_shutdown);
> > EXPORT_SYMBOL_GPL(ata_scsi_device_suspend);
> > EXPORT_SYMBOL_GPL(ata_scsi_device_resume);
> > +EXPORT_SYMBOL_GPL(ata_scsi_device_shutdown);
> [...]
>
> Side note: If you would prepare the host template in libata, you
> wouldn't need to export these and other symbols. As was AFAIR discussed
> by other people before, libata could certainly hide scsi_host_template
> from ATA drivers entirely.
OK. Thanks for your review and comments.
---
~Randy
next prev parent reply other threads:[~2006-02-16 18:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-15 19:46 [PATCH] shutdown processing Randy Dunlap
2006-02-16 8:58 ` Stefan Richter
2006-02-16 18:40 ` Randy Dunlap [this message]
2006-02-16 18:56 ` Stefan Richter
2006-02-16 19:12 ` Randy Dunlap
2006-02-17 19:15 ` Stefan Richter
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=20060216104007.67cf613f.randy_d_dunlap@linux.intel.com \
--to=randy_d_dunlap@linux.intel.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=stefanr@s5r6.in-berlin.de \
/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;
as well as URLs for NNTP newsgroup(s).