linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: OMAP2+: fix naming collision of variable nr_irqs
Date: Tue, 26 Jun 2012 03:50:36 -0700	[thread overview]
Message-ID: <20120626105035.GC31393@atomide.com> (raw)
In-Reply-To: <1340620000-27074-1-git-send-email-svenkatr@ti.com>

* Venkatraman S <svenkatr@ti.com> [120625 03:31]:
> Using nr_irqs as local variable name triggers the sparse warning..
> ./arch/arm/mach-omap2/irq.c:265:6: warning: symbol 'nr_irqs' shadows an earlier one
> ./linux/include/linux/irqnr.h:26:12: originally declared here

Thanks applying both into fixes-non-critical.

Tony

      parent reply	other threads:[~2012-06-26 10:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-25 10:26 [PATCH 1/2] ARM: OMAP2+: fix naming collision of variable nr_irqs Venkatraman S
2012-06-25 10:26 ` [PATCH 2/2] ARM: OMAP2+: use proper type for keymap data in boardfiles Venkatraman S
2012-06-26 10:50 ` Tony Lindgren [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=20120626105035.GC31393@atomide.com \
    --to=tony@atomide.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).