From: Felipe Balbi <me@felipebalbi.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Felipe Balbi <balbi@ti.com>, Tony Lindgren <tony@atomide.com>,
Linux OMAP Mailing List <linux-omap@vger.kernel.org>,
Russell King <linux@arm.linux.org.uk>,
Linux ARM Kernel Mailing List
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 2/4] arm: Kconfig: remove duplicated GENERIC_HARDIRQS entry
Date: Tue, 04 Jan 2011 16:09:13 +0200 [thread overview]
Message-ID: <1294150153.1822.10.camel@eowin> (raw)
In-Reply-To: <20110104140031.GE25121@pengutronix.de>
On Tue, 2011-01-04 at 15:00 +0100, Uwe Kleine-König wrote:
> On Tue, Jan 04, 2011 at 02:02:55PM +0200, Felipe Balbi wrote:
> > GENERIC_HARDIRQS is defined under kernel/irq/Kconfig,
> > so it's safe to drop the duplicated entry and simply
> > select HAVE_GENERIC_HARDIRQS.
> >
> > Signed-off-by: Felipe Balbi <balbi@ti.com>
> > ---
> > arch/arm/Kconfig | 8 +-------
> > 1 files changed, 1 insertions(+), 7 deletions(-)
> >
> > diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
> > index d56d21c0..e6f0f8b 100644
> > --- a/arch/arm/Kconfig
> > +++ b/arch/arm/Kconfig
> > @@ -15,6 +15,7 @@ config ARM
> > select HAVE_FTRACE_MCOUNT_RECORD if (!XIP_KERNEL)
> > select HAVE_DYNAMIC_FTRACE if (!XIP_KERNEL)
> > select HAVE_GENERIC_DMA_COHERENT
> > + select HAVE_GENERIC_HARDIRQS
> > select HAVE_KERNEL_GZIP
> > select HAVE_KERNEL_LZO
> > select HAVE_KERNEL_LZMA
> > @@ -88,10 +89,6 @@ config MCA
> > <file:Documentation/mca.txt> (and especially the web page given
> > there) before attempting to build an MCA bus kernel.
> >
> > -config GENERIC_HARDIRQS
> > - bool
> > - default y
> > -
> > config STACKTRACE_SUPPORT
> > bool
> > default y
> > @@ -171,9 +168,6 @@ config FIQ
> > config ARCH_MTD_XIP
> > bool
> >
> > -config GENERIC_HARDIRQS_NO__DO_IRQ
> > - def_bool y
> > -
> You didn't mention this change in the commit log. Is this duplicated,
> too or did it just slip through?
Yes it is. My bad. Do I need to update the patch ? I can do it tomorrow.
--
balbi
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-01-04 14:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-04 12:02 [PATCH 0/4] ARM IRQ Changes Felipe Balbi
2011-01-04 12:02 ` [PATCH 1/4] arm: omap: gpio: don't access irq_desc array directly Felipe Balbi
2011-01-05 0:24 ` Kevin Hilman
2011-01-05 6:47 ` Felipe Balbi
2011-01-05 17:11 ` Kevin Hilman
2011-01-04 12:02 ` [PATCH 2/4] arm: Kconfig: remove duplicated GENERIC_HARDIRQS entry Felipe Balbi
2011-01-04 14:00 ` Uwe Kleine-König
2011-01-04 14:09 ` Felipe Balbi [this message]
2011-01-04 17:33 ` Russell King - ARM Linux
2011-01-04 20:54 ` Uwe Kleine-König
2011-01-05 6:51 ` Felipe Balbi
2011-01-04 12:02 ` [PATCH 3/4] arm: Kconfig: remove duplicated SPARSE_IRQ entry Felipe Balbi
2011-01-04 12:02 ` [PATCH 4/4] arm: Kconfig: allow OMAP to use sparse IRQ numbering Felipe Balbi
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=1294150153.1822.10.camel@eowin \
--to=me@felipebalbi.com \
--cc=balbi@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=tony@atomide.com \
--cc=u.kleine-koenig@pengutronix.de \
/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