mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Vladimir Murzin <vladimir.murzin@arm.com>
Cc: linux-kernel@vger.kernel.org, Marc Zyngier <marc.zyngier@arm.com>
Subject: Re: [PATCH] genirq: fix comment to __handle_domain_irq
Date: Fri, 10 Feb 2017 12:37:49 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.20.1702101236050.4036@nanos> (raw)
In-Reply-To: <1484053380-818-1-git-send-email-vladimir.murzin@arm.com>

On Tue, 10 Jan 2017, Vladimir Murzin wrote:
> NULL domain is valid parameter and handled as default irq domain by
> irq_find_mapping(). Instead of using NULL domain, dedicated "lookup"
> parameter should be used to indicate whether conversion of HW
> interrupt to the logical one is needed or not.
> 
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Marc Zyngier <marc.zyngier@arm.com>
> Signed-off-by: Vladimir Murzin <vladimir.murzin@arm.com>
> ---
>  include/linux/irqdesc.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/include/linux/irqdesc.h b/include/linux/irqdesc.h
> index c9be579..8f5f7d9 100644
> --- a/include/linux/irqdesc.h
> +++ b/include/linux/irqdesc.h
> @@ -156,7 +156,7 @@ static inline void generic_handle_irq_desc(struct irq_desc *desc)
>  /*
>   * Convert a HW interrupt number to a logical one using a IRQ domain,
>   * and handle the result interrupt number. Return -EINVAL if
> - * conversion failed. Providing a NULL domain indicates that the
> + * conversion failed. Providing lookup set to false indicates that the
>   * conversion has already been done.
>   */

We should just remove that comment completely as we have a proper and
correct kernel doc annotation for that function where its
implemented. Having two places to document stuff is just wrong.

Thanks,

	tglx

      reply	other threads:[~2017-02-10 12:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-10 13:03 Vladimir Murzin
2017-02-10 11:37 ` Thomas Gleixner [this message]

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=alpine.DEB.2.20.1702101236050.4036@nanos \
    --to=tglx@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.zyngier@arm.com \
    --cc=vladimir.murzin@arm.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®