From: "Andrew Chew" <achew@nvidia.com>
To: "Jeff Garzik" <jgarzik@pobox.com>
Cc: <linux-kernel@vger.kernel.org>, <linux-ide@vger.kernel.org>
Subject: RE: [PATCH 2.6.8-rc2] sata_nv.c
Date: Thu, 5 Aug 2004 15:06:27 -0700 [thread overview]
Message-ID: <DBFABB80F7FD3143A911F9E6CFD477B03F9623@hqemmail02.nvidia.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 506 bytes --]
> Andrew Chew wrote:
> > A minor change to libata-core.c needs to accompany this
> patch. This
> > is in regards to the function ata_pci_remove_one(), where the
> > host_set->ops->host_stop(host_set) needs to occur before the
> > iounmap(host_set->mmio_base). This is because sata_nv's host_stop
> > callback needs access to the iomapped region.
Jeff Garzik wrote:
> Do you want to send a separate patch for this? I don't see
> that change
> in the attached patch.
Attached patch.
[-- Attachment #2: libata-core_2-6.diff --]
[-- Type: application/octet-stream, Size: 488 bytes --]
--- linux-2.6.8-rc2/drivers/scsi/libata-core.c 2004-08-05 14:17:30.000000000 -0700
+++ linux/drivers/scsi/libata-core.c 2004-07-27 14:42:06.000000000 -0700
@@ -3251,10 +3251,10 @@
}
free_irq(host_set->irq, host_set);
- if (host_set->mmio_base)
- iounmap(host_set->mmio_base);
if (host_set->ops->host_stop)
host_set->ops->host_stop(host_set);
+ if (host_set->mmio_base)
+ iounmap(host_set->mmio_base);
for (i = 0; i < host_set->n_ports; i++) {
ap = host_set->ports[i];
next reply other threads:[~2004-08-05 22:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-05 22:06 Andrew Chew [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-05 21:31 Andrew Chew
2004-08-05 21:53 ` Jeff Garzik
2004-07-27 20:26 Andrew Chew
2004-07-27 18:45 Andrew Chew
2004-07-27 18:55 ` Jeff Garzik
2004-07-22 21:38 Andrew Chew
2004-07-27 17:07 ` Jeff Garzik
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=DBFABB80F7FD3143A911F9E6CFD477B03F9623@hqemmail02.nvidia.com \
--to=achew@nvidia.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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 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®