[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <17853.7463.911235.324340@cargo.ozlabs.ibm.com>
Date: Mon, 29 Jan 2007 09:01:11 +1100
From: Paul Mackerras <paulus@...ba.org>
To: ebiederm@...ssion.com (Eric W. Biederman)
Cc: Greg Kroah-Hartman <greg@...ah.com>,
Tony Luck <tony.luck@...el.com>,
Grant Grundler <grundler@...isc-linux.org>,
Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org,
Kyle McMartin <kyle@...isc-linux.org>, linuxppc-dev@...abs.org,
Brice Goglin <brice@...i.com>, shaohua.li@...el.com,
linux-pci@...ey.karlin.mff.cuni.cz,
"David S. Miller" <davem@...emloft.net>
Subject: Re: [PATCH 1/6] msi: Kill msi_lookup_irq
Eric W. Biederman writes:
> @@ -693,15 +664,14 @@ int pci_enable_msi(struct pci_dev* dev)
> if (!pos)
> return -EINVAL;
>
> - WARN_ON(!msi_lookup_irq(dev, PCI_CAP_ID_MSI));
> + WARN_ON(!!dev->msi_enabled);
Minor nit: what's wrong with just WARN_ON(dev->msi_enabled) ?
Also here:
> @@ -836,16 +811,14 @@ int pci_enable_msix(struct pci_dev* dev, struct msix_entry *entries, int nvec)
> return -EINVAL; /* duplicate entry */
> }
> }
> - temp = dev->irq;
> - WARN_ON(!msi_lookup_irq(dev, PCI_CAP_ID_MSIX));
> + WARN_ON(!!dev->msix_enabled);
Paul.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists