[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALRxmdB0Ltt3_G=D4i7x47pHCtCKo8RHgn-hgN+u=px22dimOA@mail.gmail.com>
Date: Tue, 5 Aug 2014 17:35:04 -0500
From: Stuart Yoder <b08248@...il.com>
To: Yijing Wang <wangyijing@...wei.com>
Cc: linux-kernel@...r.kernel.org, Xinwei Hu <huxinwei@...wei.com>,
Wuyun <wuyun.wu@...wei.com>, Bjorn Helgaas <bhelgaas@...gle.com>,
linux-pci@...r.kernel.org, Paul.Mundt@...wei.com,
"James E.J. Bottomley" <jejb@...isc-linux.org>,
Marc Zyngier <marc.zyngier@....com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
Russell King <linux@....linux.org.uk>,
linux-arch@...r.kernel.org, arnab.basu@...escale.com,
virtualization@...ts.linux-foundation.org,
Hanjun Guo <guohanjun@...wei.com>
Subject: Re: [RFC PATCH 03/11] PCI/MSI: Refactor pci_dev_msi_enabled()
On Fri, Jul 25, 2014 at 10:08 PM, Yijing Wang <wangyijing@...wei.com> wrote:
> Pci_dev_msi_enabled() is used to check whether device
> MSI/MSIX enabled. Refactor this function to suuport
> checking only device MSI or MSIX enabled.
>
> Signed-off-by: Yijing Wang <wangyijing@...wei.com>
So this patch refactors things so that checks like this:
> - if (!dev->msi_enabled)
are moved into a function:
> + if (!pci_dev_msi_enabled(dev, MSI_TYPE))
Can you explain a bit more why this needed. Is it just cleanup?
Thanks,
Stuart
--
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