From: Grant Likely <grant.likely@secretlab.ca>
To: John Linn <john.linn@xilinx.com>
Cc: linuxppc-dev@ozlabs.org, akonovalov@ru.mvista.com,
dbrownell@users.sourceforge.net
Subject: Re: [PATCH] Xilinx: SPI: driver not releasing memory
Date: Sat, 28 Feb 2009 21:09:09 -0700 [thread overview]
Message-ID: <fa686aa40902282009y6b96129ct7cc602158129dc8f@mail.gmail.com> (raw)
In-Reply-To: <20090227235456.4DED2448057@mail135-wa4.bigfish.com>
On Fri, Feb 27, 2009 at 4:54 PM, John Linn <john.linn@xilinx.com> wrote:
> The driver was not releasing memory when it was removed or
> when there was a failure during probe. This fixes it.
>
> Signed-off-by: John Linn <john.linn@xilinx.com>
Looks good.
Acked-by: Grant Likely <grant.likely@secretlab.ca>
I'll pick this up into my -next branch and ask Ben to pull it in the
next week or so.
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next prev parent reply other threads:[~2009-03-01 4:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-27 23:54 [PATCH] Xilinx: SPI: driver not releasing memory John Linn
2009-03-01 4:09 ` Grant Likely [this message]
2009-03-06 15:49 ` Grant Likely
2009-03-06 20:00 ` David Brownell
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=fa686aa40902282009y6b96129ct7cc602158129dc8f@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=akonovalov@ru.mvista.com \
--cc=dbrownell@users.sourceforge.net \
--cc=john.linn@xilinx.com \
--cc=linuxppc-dev@ozlabs.org \
/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).