linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org, r54964@freescale.com
Subject: Re: [PATCH 4/4] Add irq debugfs and virq_mapping for getting the virq to irq host's hwirq mapping list.
Date: Wed, 21 Mar 2007 22:45:42 +0100	[thread overview]
Message-ID: <016c9b6f097a7688dd80ff73bb68a61b@kernel.crashing.org> (raw)
In-Reply-To: <1174508651.10836.4.camel@localhost.localdomain>

>> Or put the whole IRQ tree under sysfs generically...
>
> Except that there is no such thing as an IRQ tree in the generic 
> code...

Darn, I thought the whole cascading thing was done in
generic code now.  Oh well...


Segher

      reply	other threads:[~2007-03-21 21:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-16  4:38 [PATCH 1/4] Add a new member 'name' to structure irq_host Zhang Wei
2007-03-16  4:38 ` [PATCH 2/4] Add i8259 host name Zhang Wei
2007-03-16  4:38   ` [PATCH 3/4] Add mpic " Zhang Wei
2007-03-16  4:38     ` [PATCH 4/4] Add irq debugfs and virq_mapping for getting the virq to irq host's hwirq mapping list Zhang Wei
2007-03-20  3:03       ` Michael Ellerman
2007-03-20  9:51         ` [PATCH 4/4] Add irq debugfs and virq_mapping for getting thevirq " Zhang Wei-r63237
2007-03-27  3:21           ` Michael Ellerman
2007-03-21 14:17         ` [PATCH 4/4] Add irq debugfs and virq_mapping for getting the virq " Segher Boessenkool
2007-03-21 20:24           ` Benjamin Herrenschmidt
2007-03-21 21:45             ` Segher Boessenkool [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=016c9b6f097a7688dd80ff73bb68a61b@kernel.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=benh@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.org \
    --cc=r54964@freescale.com \
    /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).