From: Tabi Timur-B04825 <B04825@freescale.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Anton Vorontsov <avorontsov@ru.mvista.com>,
Linux/PPC Development <linuxppc-dev@lists.ozlabs.org>,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] powerpc/mpc8610_hpcd: Do not use "/" in interrupt names
Date: Mon, 9 May 2011 16:09:10 +0000 [thread overview]
Message-ID: <BANLkTi=ytcPhpYp=Mqk7fYYAv+5eqbkNww@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1105041627560.2601@ayla.of.borg>
On Wed, May 4, 2011 at 9:29 AM, Geert Uytterhoeven <geert@linux-m68k.org> w=
rote:
> It may trigger a warning in fs/proc/generic.c:__xlate_proc_name() when
> trying to add an entry for the interrupt handler to sysfs.
>
> Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
Acked-by: Timur Tabi <timur@freescale.com>
This fixes a real bug in the kernel.
--=20
Timur Tabi
Linux kernel developer at Freescale=
next prev parent reply other threads:[~2011-05-09 16:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-04 14:29 [PATCH] powerpc/mpc8610_hpcd: Do not use "/" in interrupt names Geert Uytterhoeven
2011-05-09 16:09 ` Tabi Timur-B04825 [this message]
2011-05-19 5:41 ` Kumar Gala
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='BANLkTi=ytcPhpYp=Mqk7fYYAv+5eqbkNww@mail.gmail.com' \
--to=b04825@freescale.com \
--cc=avorontsov@ru.mvista.com \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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).