From: Greg KH <gregkh@linuxfoundation.org>
To: Stefan Schmidt <stefan@osg.samsung.com>
Cc: marcel@holtmann.org, linux-wpan@vger.kernel.org,
Alexander Aring <aar@pengutronix.de>,
stable@vger.kernel.org
Subject: Re: [PATCH bluetooth 1/5] ieee802154: atusb: do not use the stack for buffers to make them DMA able
Date: Sat, 7 Jan 2017 09:52:34 +0100 [thread overview]
Message-ID: <20170107085234.GA20798@kroah.com> (raw)
In-Reply-To: <1483748337-4862-2-git-send-email-stefan@osg.samsung.com>
On Sat, Jan 07, 2017 at 01:18:53AM +0100, Stefan Schmidt wrote:
> From 4.9 we should really avoid using the stack here as this will not be DMA
> able on various platforms. This changes the buffers already being present in
> time of 4.9 being released. This should go into stable as well.
It's not just a 4.9 issue, this affects other platforms on all kernel
versions.
>
> Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
> Cc: stable@vger.kernel.org
> Signed-off-by: Stefan Schmidt <stefan@osg.samsung.com>
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
next prev parent reply other threads:[~2017-01-07 8:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-07 0:18 [pull-request bluetooth] wpan fixes for 4.10 2017-01-07 Stefan Schmidt
2017-01-07 0:18 ` [PATCH bluetooth 1/5] ieee802154: atusb: do not use the stack for buffers to make them DMA able Stefan Schmidt
2017-01-07 0:18 ` Stefan Schmidt
2017-01-07 8:52 ` Greg KH [this message]
2017-01-07 0:18 ` [PATCH bluetooth 2/5] ieee802154: atusb: make sure we set a randaom extended address if fetching fails Stefan Schmidt
2017-01-07 0:18 ` [PATCH bluetooth 3/5] ieee802154: atusb: do not use the stack for address fetching to make it DMA able Stefan Schmidt
2017-01-07 0:18 ` [PATCH bluetooth 4/5] at86rf230: Allow slow GPIO pins for "rstn" Stefan Schmidt
2017-01-07 0:18 ` [PATCH bluetooth 5/5] ieee802154: atusb: fix driver to work with older firmware versions Stefan Schmidt
2017-01-12 7:56 ` [pull-request bluetooth] wpan fixes for 4.10 2017-01-07 Stefan Schmidt
2017-01-12 21:39 ` Marcel Holtmann
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=20170107085234.GA20798@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=aar@pengutronix.de \
--cc=linux-wpan@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=stable@vger.kernel.org \
--cc=stefan@osg.samsung.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 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.