From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Vrabel Subject: Re: [PATCH 01/16] xen/events: refactor retrigger_dynirq() and resend_irq_on_evtchn() Date: Mon, 14 Oct 2013 17:35:02 +0100 Message-ID: <525C1D36.4000402@citrix.com> References: <1381236555-27493-1-git-send-email-david.vrabel@citrix.com> <1381236555-27493-2-git-send-email-david.vrabel@citrix.com> <525C14F1.3080802@oracle.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <525C14F1.3080802@oracle.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Boris Ostrovsky Cc: Jan Beulich , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On 14/10/13 16:59, Boris Ostrovsky wrote: > On 10/08/2013 08:49 AM, David Vrabel wrote: >> From: David Vrabel >> >> These two function did the same thing with different parameters, put >> the common bits in retrigger_evtchn(). >> >> This changes the return value of resend_irq_on_evtchn() but the only >> caller (in arch/ia64/xen/irq_xen.c) ignored the return value so this >> is fine. > > Not directly related to this patch, but why do we still have > arch/ia64/xen? Is anyone testing it? I only see a few superficial > changes in the log for last year, and those appear to be result of code > inspection or some global changes, not actual execution. I was going to bring it up at the Developer's meeting. I think we should think about removing it. David