From: Ingo Molnar <mingo@elte.hu>
To: Yinghai Lu <yinghai@kernel.org>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH for -tip 3/4] proc: remove ifdef CONFIG_SPARSE_IRQ from stat.c
Date: Fri, 26 Dec 2008 09:49:58 +0100 [thread overview]
Message-ID: <20081226084958.GD755@elte.hu> (raw)
In-Reply-To: <86802c440812252159v6129a385qb900be42845ac90a@mail.gmail.com>
* Yinghai Lu <yinghai@kernel.org> wrote:
> > hm, instead, How about following patch?
> >
> > =======
> > Subject: [PATCH] proc: remove ifdef CONFIG_SPARSE_IRQ from stat.c
> > Impact: cleanup
> nice. much clean.
applied all four patches to tip/irq/sparseirq:
18eefed: irq: simplify for_each_irq_desc() usage
26ddd8d: proc: remove ifdef CONFIG_SPARSE_IRQ from stat.c
f9af0e7: irq: for_each_irq_desc() move to irqnr.h
51bc39f: hrtimer: remove #include <linux/irq.h>
the whole series is very nice and removes quite a bit of irq_desc usage
complexity. Thanks guys,
Ingo
next prev parent reply other threads:[~2008-12-26 8:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-26 3:21 [PATCH for -tip 0/4] various irq cleanups KOSAKI Motohiro
2008-12-26 3:23 ` [PATCH for -tip 1/4] hrtimer: remove #include <linux/irq.h> KOSAKI Motohiro
2008-12-26 3:24 ` [PATCH for -tip 2/4] irq: for_each_irq_desc() move to irqnr.h KOSAKI Motohiro
2008-12-26 3:28 ` [PATCH for -tip 3/4] proc: remove ifdef CONFIG_SPARSE_IRQ from stat.c KOSAKI Motohiro
2008-12-26 4:18 ` Yinghai Lu
2008-12-26 4:21 ` KOSAKI Motohiro
2008-12-26 4:36 ` Yinghai Lu
2008-12-26 5:24 ` KOSAKI Motohiro
2008-12-26 5:59 ` Yinghai Lu
2008-12-26 8:49 ` Ingo Molnar [this message]
2008-12-26 3:29 ` [PATCH for -tip 4/4] irq: for_each_irq_desc() makes simplify KOSAKI Motohiro
2008-12-26 4:23 ` Yinghai Lu
2009-01-01 18:05 ` Raja R Harinath
2009-01-02 5:56 ` KOSAKI Motohiro
2009-01-03 18:11 ` KOSAKI Motohiro
2009-01-07 22:18 ` Ingo Molnar
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=20081226084958.GD755@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yinghai@kernel.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