From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Segher Boessenkool <segher@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: Thu, 22 Mar 2007 07:24:11 +1100 [thread overview]
Message-ID: <1174508651.10836.4.camel@localhost.localdomain> (raw)
In-Reply-To: <65a42fd7d277db5f565849a07d8dea90@kernel.crashing.org>
On Wed, 2007-03-21 at 15:17 +0100, Segher Boessenkool wrote:
> >> This patch adds 'irq' directory into the root debugfs and
> >> virq_mapping for getting the virq to
> >> irq host's hwirq mapping list.
> >
> > Minor nit. Should we be creating a 'powerpc' directory first, and
> > putting the 'irq' file under that? Otherwise we risk clashing with some
> > generic code that creates a file called 'irq' in debugfs.
>
> Or put the whole IRQ tree under sysfs generically...
Except that there is no such thing as an IRQ tree in the generic code...
Ben.
next prev parent reply other threads:[~2007-03-21 20:24 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 [this message]
2007-03-21 21:45 ` Segher Boessenkool
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=1174508651.10836.4.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=r54964@freescale.com \
--cc=segher@kernel.crashing.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).