From: Greg KH <gregkh@linuxfoundation.org>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: arm@vger.kernel.org, djbw@fb.com, vinod.koul@intel.com,
linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] dma: tegra: fix interrupt name issue with apb dma.
Date: Wed, 3 Oct 2012 11:17:57 -0700 [thread overview]
Message-ID: <20121003181757.GA24871@kroah.com> (raw)
In-Reply-To: <1349284687-22311-1-git-send-email-ldewangan@nvidia.com>
On Wed, Oct 03, 2012 at 10:48:07PM +0530, Laxman Dewangan wrote:
> When watching the interrupts through /proc/interrupts,
> the name of the interrupts are blank or garbage. The
> reason is the pointer passed for devname during irq
> registration is stack and so it get changed after
> dma registration completes.
> Allocate the pointer as part of dma channel and pass
> this pointer as the devname for irq registration to
> avoid change of name.
>
> Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
> ---
> drivers/dma/tegra20-apb-dma.c | 6 +++---
> 1 files changed, 3 insertions(+), 3 deletions(-)
<formletter>
This is not the correct way to submit patches for inclusion in the
stable kernel tree. Please read Documentation/stable_kernel_rules.txt
for how to do this properly.
</formletter>
next prev parent reply other threads:[~2012-10-03 18:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-03 17:18 [PATCH] dma: tegra: fix interrupt name issue with apb dma Laxman Dewangan
2012-10-03 18:17 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-10-03 17:21 Laxman Dewangan
[not found] ` <1349284913-22350-1-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-10-03 20:53 ` Stephen Warren
[not found] ` <506CA5D8.1050201-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-10-04 8:16 ` Arnd Bergmann
2012-10-04 8:26 ` Koul, Vinod
[not found] ` <8D3F6266AEB6384E807C6FFC6FE195E30181BBF0-yHIBzpp8AekElmVAvsQTrbfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2012-10-04 15:23 ` Vinod Koul
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=20121003181757.GA24871@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arm@vger.kernel.org \
--cc=djbw@fb.com \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=vinod.koul@intel.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).