All of lore.kernel.org
 help / color / mirror / Atom feed
From: nsekhar@ti.com (Nori, Sekhar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/4] ARM: davinci: Check for NULL return from irq_alloc_generic_chip
Date: Thu, 14 Jul 2011 10:50:38 +0530	[thread overview]
Message-ID: <B85A65D85D7EB246BE421B3FB0FBB593024DB11B2B@dbde02.ent.ti.com> (raw)
In-Reply-To: <1310509910-4244-1-git-send-email-toddpoynor@google.com>

Hi Todd,

On Wed, Jul 13, 2011 at 04:01:50, Todd Poynor wrote:
> Signed-off-by: Todd Poynor <toddpoynor@google.com>

Can you please include some patch description
(even if it turns out to be a restatement of
patch headline)?

Also, in general, including some background on how
you discovered the issue and how it affected you
can help determine the priority of the fix.

Thanks,
Sekhar

> ---
>  arch/arm/mach-davinci/irq.c |    7 +++++++
>  1 files changed, 7 insertions(+), 0 deletions(-)
> 
> diff --git a/arch/arm/mach-davinci/irq.c b/arch/arm/mach-davinci/irq.c
> index bfe68ec..ab7f688 100644
> --- a/arch/arm/mach-davinci/irq.c
> +++ b/arch/arm/mach-davinci/irq.c
> @@ -52,6 +52,13 @@ davinci_alloc_gc(void __iomem *base, unsigned int irq_start, unsigned int num)
>  	struct irq_chip_type *ct;
>  
>  	gc = irq_alloc_generic_chip("AINTC", 1, irq_start, base, handle_edge_irq);
> +
> +	if (!gc) {
> +		pr_err("%s: irq_alloc_generic_chip for IRQ %u failed\n",
> +		       __func__, irq_start);
> +		return;
> +	}
> +
>  	ct = gc->chip_types;
>  	ct->chip.irq_ack = irq_gc_ack;
>  	ct->chip.irq_mask = irq_gc_mask_clr_bit;
> -- 
> 1.7.3.1
> 
> 

      parent reply	other threads:[~2011-07-14  5:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-12 22:31 [PATCH 1/4] ARM: davinci: Check for NULL return from irq_alloc_generic_chip Todd Poynor
2011-07-13 10:46 ` Sergei Shtylyov
2011-07-14  5:20 ` Nori, Sekhar [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=B85A65D85D7EB246BE421B3FB0FBB593024DB11B2B@dbde02.ent.ti.com \
    --to=nsekhar@ti.com \
    --cc=linux-arm-kernel@lists.infradead.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.