All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
	Tim Deegan <tim@xen.org>, Keir Fraser <keir@xen.org>,
	Ian Campbell <Ian.Campbell@citrix.com>,
	Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: [PATCH] xen: cleanup unused request{_dt, }_irq() parameter
Date: Wed, 7 Aug 2013 13:13:42 +0100	[thread overview]
Message-ID: <520239F6.8050005@citrix.com> (raw)
In-Reply-To: <5202550802000078000E9EA1@nat28.tlf.novell.com>

On 07/08/13 13:09, Jan Beulich wrote:
>>>> On 07.08.13 at 13:59, Andrew Cooper <andrew.cooper3@citrix.com> wrote:
>> On 07/08/13 08:42, Jan Beulich wrote:
>>>>>> On 06.08.13 at 19:42, Andrew Cooper <andrew.cooper3@citrix.com> wrote:
>>>> The irqflags parameter appears to be an unused vestigial parameter right 
>> from
>>>> the integration of the IOMMU code in 2007.  The parameter is 0 at all
>>>> callsites and never used.
>>>>
>>>> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
>>> Reviewed-by: Jan Beulich <JBeulich@suse.com>
>>>
>>> If I were to commit it - with the appropriate acks - I'd also cleanup
>>> the white space damage left in place:
>>>
>>>> --- a/xen/arch/x86/irq.c
>>>> +++ b/xen/arch/x86/irq.c
>>>> @@ -951,7 +951,7 @@ __initcall(irq_ratelimit_init);
>>>>  
>>>>  int __init request_irq(unsigned int irq,
>>>>          void (*handler)(int, void *, struct cpu_user_regs *),
>>>> -        unsigned long irqflags, const char * devname, void *dev_id)
>>>> +        const char * devname, void *dev_id)
>>> Here ...
>>>
>>>> --- a/xen/include/xen/irq.h
>>>> +++ b/xen/include/xen/irq.h
>>>> @@ -93,7 +93,7 @@ extern int setup_irq(unsigned int irq, struct irqaction *);
>>>>  extern void release_irq(unsigned int irq);
>>>>  extern int request_irq(unsigned int irq,
>>>>                 void (*handler)(int, void *, struct cpu_user_regs *),
>>>> -               unsigned long irqflags, const char * devname, void *dev_id);
>>>> +               const char * devname, void *dev_id);
>>> ... and here.
>>>
>>> I'd encourage you to in the future do such obvious cleanup on
>>> code you touch anyway.
>>>
>>> Jan
>>>
>> Certainly (I tend to, but it slipped my mind this time) - I shall submit v2
> No need to do so - as said, if I'm going to be the one to apply this
> (likely), I'll do that cleanup as I go.
>
> Jan
>
Ok - thanks.

~Andrew

  reply	other threads:[~2013-08-07 12:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-06 17:42 [PATCH] xen: cleanup unused request{_dt, }_irq() parameter Andrew Cooper
2013-08-07  7:42 ` Jan Beulich
2013-08-07 11:59   ` Andrew Cooper
2013-08-07 12:09     ` Jan Beulich
2013-08-07 12:13       ` Andrew Cooper [this message]
2013-08-07  8:33 ` Ian Campbell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=520239F6.8050005@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=Stefano.Stabellini@eu.citrix.com \
    --cc=keir@xen.org \
    --cc=tim@xen.org \
    --cc=xen-devel@lists.xenproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.