On Thu, Sep 25, 2014 at 11:14:11AM +0800, Yijing Wang wrote:
Msi_chip functions setup_irq/teardown_irq rarely use msi_chip
argument.
That's not true. Out of the four drivers that you modify two use the
parameter. And the two that don't probably should be using it too.
50% is not rarely. =)
On Thu, 25 Sep 2014, Thierry Reding wrote:
On Thu, Sep 25, 2014 at 11:14:11AM +0800, Yijing Wang wrote:
Msi_chip functions setup_irq/teardown_irq rarely use msi_chip
argument.
That's not true. Out of the four drivers that you modify two use the
parameter. And the two that don't probably
On 2014/9/25 15:15, Thierry Reding wrote:
On Thu, Sep 25, 2014 at 11:14:11AM +0800, Yijing Wang wrote:
Msi_chip functions setup_irq/teardown_irq rarely use msi_chip
argument.
That's not true. Out of the four drivers that you modify two use the
parameter. And the two that don't probably
On 2014/9/25 18:20, Thomas Gleixner wrote:
On Thu, 25 Sep 2014, Thierry Reding wrote:
On Thu, Sep 25, 2014 at 11:14:11AM +0800, Yijing Wang wrote:
Msi_chip functions setup_irq/teardown_irq rarely use msi_chip
argument.
That's not true. Out of the four drivers that you modify two use the
Msi_chip functions setup_irq/teardown_irq rarely use msi_chip
argument. We can look up msi_chip pointer by the device pointer
or irq number, so clean up msi_chip argument.
Signed-off-by: Yijing Wang wangyij...@huawei.com
CC: Thierry Reding thierry.red...@gmail.com
CC: Thomas Petazzoni
