From: Chris Metcalf <cmetcalf@tilera.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [patch 0/2] tile: Final irq bits for .39
Date: Fri, 25 Mar 2011 13:31:40 -0400 [thread overview]
Message-ID: <4D8CD17C.9040104@tilera.com> (raw)
In-Reply-To: <20110325141938.846639464@linutronix.de>
On 3/25/2011 10:21 AM, Thomas Gleixner wrote:
> Chris,
>
> the series converts the irq functions to the new function names and
> makes use of the generic show_interrupts() implementation.
>
> Can you please ack or send it to Linus yourself ?
Acked-by: Chris Metcalf <cmetcalf@tilera.com>
I'd probably prefer you send it, but if you'd like me to, let me know. I
confirmed that I can build and boot with your change, and that
/proc/interrupts produces something reasonable.
Well, no less reasonable than usual for our chip, anyway; this is for a
chip on a PCIe board, so no PCI or other interrupt sources plugged in:
# cat /proc/interrupts
CPU0 CPU1 CPU2 CPU3 CPU4 CPU5 CPU6 CPU7 CPU8 CPU9 CPU10 CPU11 CPU12 CPU13 CPU14 CPU15 CPU16 CPU17 CPU18 CPU19 CPU20 CPU21 CPU22 CPU23 CPU24 CPU25 CPU26 CPU27 CPU28 CPU29 CPU30 CPU31 CPU32 CPU33 CPU34 CPU35 CPU36 CPU37 CPU38 CPU39 CPU40 CPU41 CPU42 CPU43 CPU44 CPU45 CPU46 CPU47 CPU48 CPU49 CPU50 CPU51 CPU52 CPU53 CPU54 CPU55 CPU58
1: 479 313 8 3 3 3 3 3 3 3 4 4 4 4 4 4 10 4 4 4 4 4 4 4 4 4 3 39 84 35 9 5 5 3 3 3 3 3 3 3 3 9 3 4 4 4 4 10 4 4 109 4 4 4 4 4 134 tile_irq_chip resched
--
Chris Metcalf, Tilera Corp.
http://www.tilera.com
next prev parent reply other threads:[~2011-03-25 17:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-25 14:21 [patch 0/2] tile: Final irq bits for .39 Thomas Gleixner
2011-03-25 14:21 ` [patch 1/2] tile: Convert to new irq function names Thomas Gleixner
2011-03-25 14:21 ` [patch 2/2] tile: Use generic show_interupts() Thomas Gleixner
2011-03-25 17:31 ` Chris Metcalf [this message]
2011-03-25 17:54 ` [patch 0/2] tile: Final irq bits for .39 Thomas Gleixner
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=4D8CD17C.9040104@tilera.com \
--to=cmetcalf@tilera.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.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