From: Greg KH <gregkh@suse.de>
To: "Mike Miller (OS Dev)" <mikem@beardog.cca.cpqcorp.net>
Cc: Christoph Hellwig <hch@infradead.org>,
akpm@osdl.org, jens.axboe@oracle.com,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [Patch 2/2] cciss: add shutdown support (replaces reboot notifier)
Date: Thu, 22 Feb 2007 15:08:30 -0800 [thread overview]
Message-ID: <20070222230830.GA28128@suse.de> (raw)
In-Reply-To: <20070222215611.GB14162@beardog.cca.cpqcorp.net>
On Thu, Feb 22, 2007 at 03:56:11PM -0600, Mike Miller (OS Dev) wrote:
> On Thu, Feb 22, 2007 at 09:45:02PM +0000, Christoph Hellwig wrote:
> > On Thu, Feb 22, 2007 at 03:38:45PM -0600, Mike Miller (OS Dev) wrote:
> > > Patch 2/2
> > >
> > > This adds support for struct pci_driver shutdown and negates the previous NAK'ed
> > > reboot_notifier patch. It's much easier, wish I had know about this before. Thanks to
> > > Christoph for pointing this out.
> >
> > Just sondering, where should we have put information about this so driver
> > writers/maintainers like you would have found it easily?
> >
> Excellent question. I wish I had a good answer. It's pretty difficult to monitor
> everything going on, especially when I also have to consider HP's schedule and those
> of our partners.
It is properly documented in Documentation/pci.txt as to how to do
this...
thanks,
greg k-h
next prev parent reply other threads:[~2007-02-22 23:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-22 21:38 [Patch 2/2] cciss: add shutdown support (replaces reboot notifier) Mike Miller (OS Dev)
2007-02-22 21:45 ` Christoph Hellwig
2007-02-22 21:56 ` Mike Miller (OS Dev)
2007-02-22 23:08 ` Greg KH [this message]
2007-02-22 21:49 ` James Bottomley
2007-02-22 21:55 ` Christoph Hellwig
2007-02-22 22:38 ` Mike Miller (OS Dev)
2007-02-22 21:50 ` scott.ashcroft
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=20070222230830.GA28128@suse.de \
--to=gregkh@suse.de \
--cc=akpm@osdl.org \
--cc=hch@infradead.org \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mikem@beardog.cca.cpqcorp.net \
/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