From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: spi-devel-general@lists.sourceforge.net,
linux-kernel@vger.kernel.org,
Grant Likely <grant.likely@secretlab.ca>,
Florian Fainelli <florian@openwrt.org>
Subject: Re: [RFC PATCH] spi/bcm63xx: Ensure that memory is freed only after it is no longer used
Date: Mon, 13 Aug 2012 13:29:35 +0100 [thread overview]
Message-ID: <20120813122934.GB13446@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1344632187-9603-1-git-send-email-linux@roeck-us.net>
On Fri, Aug 10, 2012 at 01:56:27PM -0700, Guenter Roeck wrote:
> The call to spi_unregister_master() in the device remove function frees device
> memory, and with it any device local data. However, device local data is still
> accessed after the call to spi_unregister_master().
Applied, thanks.
prev parent reply other threads:[~2012-08-13 12:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-10 20:56 [RFC PATCH] spi/bcm63xx: Ensure that memory is freed only after it is no longer used Guenter Roeck
2012-08-13 12:29 ` Mark Brown [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=20120813122934.GB13446@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=florian@openwrt.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=spi-devel-general@lists.sourceforge.net \
/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).