From: Jeff Garzik <jeff@garzik.org>
To: "Wolstenholme, Daniel E" <daniel.e.wolstenholme@intel.com>
Cc: Jeremy Higdon <jeremy@sgi.com>, linux-ide@vger.kernel.org
Subject: Re: [PATCH] Add MSI support to sata_vsc driver
Date: Thu, 17 Aug 2006 19:44:11 -0400 [thread overview]
Message-ID: <44E4FF4B.6020407@garzik.org> (raw)
In-Reply-To: <87840E8EE8A8D240A13F8AA92CAB07D9024C14B3@azsmsx402>
Wolstenholme, Daniel E wrote:
> Unfortunately, I'm stuck using Lookout for now.
That's OK, this one needs another iteration anyway :)
> --------------
> diff -Naur linux-2.6.18-rc1-original/drivers/scsi/sata_vsc.c
> linux-2.6.18-rc1/drivers/scsi/sata_vsc.c
> --- linux-2.6.18-rc1-original/drivers/scsi/sata_vsc.c 2006-08-15
> 17:13:53.000000000 -0700
> +++ linux-2.6.18-rc1/drivers/scsi/sata_vsc.c 2006-08-17
> 14:29:27.000000000 -0700
> @@ -406,13 +406,17 @@
> */
> pci_write_config_byte(pdev, PCI_CACHE_LINE_SIZE, 0x80);
>
> + if (pci_enable_msi && pci_enable_msi(pdev) == 0)
pci_enable_msi is not a variable, don't test it. Just call it.
The function will always exist, even if conditionally implemented as a
macro in the no-op case.
> + probe_ent->irq_flags &= ~IRQF_SHARED;
We're doing an assignment (as you see below, from the code you
modified), and the entire struct is memset(3) to zero, so there's no
need to clear this flag. Just assign it, for the non-MSI case.
> + probe_ent->irq_flags = IRQF_SHARED;
> +
> probe_ent->sht = &vsc_sata_sht;
> probe_ent->host_flags = ATA_FLAG_SATA | ATA_FLAG_NO_LEGACY |
> ATA_FLAG_MMIO;
> probe_ent->port_ops = &vsc_sata_ops;
> probe_ent->n_ports = 4;
> probe_ent->irq = pdev->irq;
> - probe_ent->irq_flags = IRQF_SHARED;
> probe_ent->mmio_base = mmio_base;
next prev parent reply other threads:[~2006-08-17 23:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-17 21:28 [PATCH] Add MSI support to sata_vsc driver Wolstenholme, Daniel E
2006-08-17 23:44 ` Jeff Garzik [this message]
2006-08-18 0:18 ` Jeremy Higdon
-- strict thread matches above, loose matches on Subject: below --
2006-09-01 20:11 Wolstenholme, Daniel E
2006-08-25 0:58 Wolstenholme, Daniel E
2006-08-24 20:55 Wolstenholme, Daniel E
2006-08-23 23:17 Wolstenholme, Daniel E
2006-08-24 6:56 ` Jeff Garzik
[not found] <87840E8EE8A8D240A13F8AA92CAB07D9024C14A6@azsmsx402>
2006-08-17 4:07 ` Jeremy Higdon
2006-08-17 12:30 ` 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=44E4FF4B.6020407@garzik.org \
--to=jeff@garzik.org \
--cc=daniel.e.wolstenholme@intel.com \
--cc=jeremy@sgi.com \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).