From: Arnd Bergmann <arnd@arndb.de>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: Laxman Dewangan <ldewangan@nvidia.com>,
arm@kernel.org, djbw@fb.com, vinod.koul@intel.com,
linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH] dma: tegra: fix interrupt name issue with apb dma.
Date: Thu, 4 Oct 2012 08:16:35 +0000 [thread overview]
Message-ID: <201210040816.35500.arnd@arndb.de> (raw)
In-Reply-To: <506CA5D8.1050201@wwwdotorg.org>
On Wednesday 03 October 2012, Stephen Warren wrote:
> On 10/03/2012 11:21 AM, 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.
>
> (Dropping stable Cc; Olof/Arnd or Vinod, is it possible you could add
> that into the patch description when applying this?)
>
> Reported-by: Stephen Warren <swarren@nvidia.com>
> Acked-by: Stephen Warren <swarren@nvidia.com>
Should be no problem. If Vinod wants to pick it up:
Acked-by: Arnd Bergmann <arnd@arndb.de>
Note that you can configure git send-email to automatically drop
Cc's to stable@vger.kernel.org, and that the correct address
is the one with vger in it, not just stable@kernel.org.
next prev parent reply other threads:[~2012-10-04 8:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-03 17:21 [PATCH] dma: tegra: fix interrupt name issue with apb dma Laxman Dewangan
2012-10-03 20:53 ` Stephen Warren
2012-10-04 8:16 ` Arnd Bergmann [this message]
2012-10-04 8:26 ` Koul, Vinod
2012-10-04 15:23 ` Vinod Koul
-- strict thread matches above, loose matches on Subject: below --
2012-10-03 17:18 Laxman Dewangan
2012-10-03 18:17 ` Greg KH
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=201210040816.35500.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=arm@kernel.org \
--cc=djbw@fb.com \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=swarren@wwwdotorg.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