From: Grant Likely <grant.likely@secretlab.ca>
To: Mika Westerberg <mika.westerberg@linux.intel.com>,
linux-kernel@vger.kernel.org
Cc: tglx@linutronix.de, benh@kernel.crashing.org,
Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: [PATCH 1/2] irq_domain: correct the debugfs file name
Date: Tue, 10 Apr 2012 17:26:47 -0600 [thread overview]
Message-ID: <20120410232647.ACB273E081E@localhost> (raw)
In-Reply-To: <1334060743-7901-1-git-send-email-mika.westerberg@linux.intel.com>
On Tue, 10 Apr 2012 15:25:42 +0300, Mika Westerberg <mika.westerberg@linux.intel.com> wrote:
> The actual name of the irq_domain mapping debugfs file is
> "irq_domain_mapping" not "virq_mapping".
>
> Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
Applied, thanks
.g
> ---
> kernel/irq/Kconfig | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/kernel/irq/Kconfig b/kernel/irq/Kconfig
> index cf1a4a6..d1a758b 100644
> --- a/kernel/irq/Kconfig
> +++ b/kernel/irq/Kconfig
> @@ -62,7 +62,7 @@ config IRQ_DOMAIN_DEBUG
> help
> This option will show the mapping relationship between hardware irq
> numbers and Linux irq numbers. The mapping is exposed via debugfs
> - in the file "virq_mapping".
> + in the file "irq_domain_mapping".
>
> If you don't know what this means you don't need it.
>
> --
> 1.7.9.1
>
--
Grant Likely, B.Sc, P.Eng.
Secret Lab Technologies,Ltd.
prev parent reply other threads:[~2012-04-10 23:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-10 12:25 [PATCH 1/2] irq_domain: correct the debugfs file name Mika Westerberg
2012-04-10 12:25 ` [PATCH 2/2] irq_domain: fix formatting of chip data pointer in virq_debug_show() Mika Westerberg
2012-04-10 23:27 ` Grant Likely
2012-04-11 5:47 ` Grant Likely
2012-04-11 9:21 ` Mika Westerberg
2012-04-10 23:26 ` Grant Likely [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=20120410232647.ACB273E081E@localhost \
--to=grant.likely@secretlab.ca \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.