linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: lethal@linux-sh.org (Paul Mundt)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH v2] preliminary support for sparse IRQ
Date: Thu, 20 May 2010 17:37:52 +0900	[thread overview]
Message-ID: <20100520083752.GB18885@linux-sh.org> (raw)
In-Reply-To: <AANLkTikVR8z_FqB4RvRWUIv2yNWw_p6gB9JQAeAMFQjq@mail.gmail.com>

On Thu, May 20, 2010 at 04:37:16PM +0800, Eric Miao wrote:
> On Thu, May 20, 2010 at 4:28 PM, Paul Mundt <lethal@linux-sh.org> wrote:
> > On Tue, May 18, 2010 at 06:34:49PM +0800, Eric Miao wrote:
> >> commit 2e2e087d96630c95dbce57036680cf917e906cf1
> >> Author: Eric Miao <eric.y.miao@gmail.com>
> >> Date: ?? Mon Dec 28 12:59:59 2009 +0800
> >>
> >> ?? ?? [ARM] preliminary support for sparse IRQ
> >>
> >> ?? ?? So to allow NR_IRQS to be dynamic and platforms to specify the number
> >> ?? ?? of IRQs really needed.
> >>
> >> ?? ?? Signed-off-by: Eric Miao <eric.y.miao@gmail.com>
> >>
> > It would be nice to see this applied, we plan to use sparseirq
> > unconditionally for shmobile (as sh already does).
> >
> 
> Thanks Paul. Sounds like an Acked-by.

Indeed.

Acked-by: Paul Mundt <lethal@linux-sh.org>

  reply	other threads:[~2010-05-20  8:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-18 10:34 [RFC PATCH v2] preliminary support for sparse IRQ Eric Miao
2010-05-18 21:45 ` Marek Vasut
2010-05-19  6:53   ` Eric Miao
2010-05-20  8:28 ` Paul Mundt
2010-05-20  8:37   ` Eric Miao
2010-05-20  8:37     ` Paul Mundt [this message]
2010-05-21 19:46   ` Russell King - ARM Linux
2010-05-22  3:34     ` Eric Miao
2010-06-25 12:50     ` Eric Miao
2010-05-20  9:21 ` Will Deacon
     [not found] ` <3319586236559971954@unknownmsgid>
2010-05-20  9:25   ` Eric Miao
2010-05-20 10:10     ` Eric Miao

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=20100520083752.GB18885@linux-sh.org \
    --to=lethal@linux-sh.org \
    --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).