[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <53160A51.5090905@citrix.com>
Date: Tue, 4 Mar 2014 17:16:01 +0000
From: David Vrabel <david.vrabel@...rix.com>
To: <mingo@...nel.org>, <hpa@...or.com>,
<linux-kernel@...r.kernel.org>, <konrad.wilk@...cle.com>,
<peterz@...radead.org>, <xen-devel@...ts.xenproject.org>,
<tglx@...utronix.de>, <david.vrabel@...rix.com>
CC: tip-bot for Thomas Gleixner <tipbot@...or.com>,
<linux-tip-commits@...r.kernel.org>
Subject: Re: [Xen-devel] [tip:irq/core] xen: Get rid of the last irq_desc
abuse
On 04/03/14 16:41, tip-bot for Thomas Gleixner wrote:
> Commit-ID: 02893afdd310fab8f41f6afbe5233c6609ec19ed
> Gitweb: http://git.kernel.org/tip/02893afdd310fab8f41f6afbe5233c6609ec19ed
> Author: Thomas Gleixner <tglx@...utronix.de>
> AuthorDate: Sun, 23 Feb 2014 21:40:20 +0000
> Committer: Thomas Gleixner <tglx@...utronix.de>
> CommitDate: Tue, 4 Mar 2014 17:37:53 +0100
>
> xen: Get rid of the last irq_desc abuse
>
> Warn if any PIRQ cannot be bound to an event channel. Remove the check
> for irq_desc->action. This hypercall never fails in practice so we can
> emit a warning unconditionally.
>
> Remove a check for a valid irq desc. The only caller of
> xen_destroy_irq() will only do so if the irq was previously fully
> setup, which means the descriptor has been allocated as well.
Reviewed-by: David Vrabel <david.vrabel@...rix.com>
Thanks.
David
--
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