From: Alan Cox <alan@linux.intel.com>
To: dave@gnu.org
Cc: jianwei.yang@intel.com, gregkh@suse.de,
linux-serial@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] serial: max3107: Fix memory leaks when returning on error
Date: Tue, 14 Sep 2010 14:45:28 +0100 [thread overview]
Message-ID: <20100914144528.77ee7a6f@linux.intel.com> (raw)
In-Reply-To: <1284394091.2055.5.camel@cowboy>
On Mon, 13 Sep 2010 12:08:11 -0400
Davidlohr Bueso <dave@gnu.org> wrote:
> [PATCH] serial: max3107: Fix memory leaks in max3107_probe() when
> returning on error.
>
> Signed-off-by: Davidlohr Bueso <dave@gnu.org>
Acked-by: Alan Cox <alan@linux.intel.com>
next prev parent reply other threads:[~2010-09-14 14:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-13 16:08 [PATCH] serial: max3107: Fix memory leaks when returning on error Davidlohr Bueso
2010-09-14 13:45 ` Alan Cox [this message]
2010-09-21 20:47 ` patch "serial: max3107: Fix memory leaks when returning on error" added to gregkh-2.6 tree gregkh
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=20100914144528.77ee7a6f@linux.intel.com \
--to=alan@linux.intel.com \
--cc=dave@gnu.org \
--cc=gregkh@suse.de \
--cc=jianwei.yang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.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 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.