From: Gustavo Padovan <gustavo@padovan.org>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v2] ath3k: don't use stack memory for DMA
Date: Tue, 9 Jul 2013 16:25:46 +0100 [thread overview]
Message-ID: <20130709152546.GB1772@joana> (raw)
In-Reply-To: <20130708082722.GB1569@redhat.com>
Hi Stanislaw,
* Stanislaw Gruszka <sgruszka@redhat.com> [2013-07-08 10:27:23 +0200]:
> Memory allocated by vmalloc (including stack) can not be used for DMA,
> i.e. data pointer on usb_control_msg() should not point to stack memory.
>
> Resolves:
> https://bugzilla.redhat.com/show_bug.cgi?id=977558
>
> Reported-and-tested-by: Andy Lawrence <dr.diesel@gmail.com>
> Signed-off-by: Stanislaw Gruszka <sgruszka@redhat.com>
> ---
> drivers/bluetooth/ath3k.c | 38 +++++++++++++++++++++++++++++---------
> 1 file changed, 29 insertions(+), 9 deletions(-)
Patch has been applied to bluetooth-next. Thanks.
Gustavo
prev parent reply other threads:[~2013-07-09 15:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 9:48 [PATCH] ath3k: don't use stack memory for DMA Stanislaw Gruszka
2013-07-07 19:40 ` Gustavo Padovan
2013-07-08 8:27 ` [PATCH v2] " Stanislaw Gruszka
2013-07-09 15:25 ` Gustavo Padovan [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=20130709152546.GB1772@joana \
--to=gustavo@padovan.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=sgruszka@redhat.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