From: Adam Belay <ambx1@neo.rr.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PnP Changes for 2.5.66
Date: Tue, 25 Mar 2003 22:34:26 +0000 [thread overview]
Message-ID: <20030325223426.GE1083@neo.rr.com> (raw)
In-Reply-To: <20030325223319.GC1083@neo.rr.com>
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet 1.985.1.94 -> 1.985.1.95
# sound/isa/als100.c 1.9 -> 1.10
#
# The following is the BitKeeper ChangeSet Log
# --------------------------------------------
# 03/03/24 ambx1@neo.rr.com 1.985.1.95
# ALS100 Memory Leak Fix
#
# This trivial patch adds a missing kfree, the leak occurs when
# pnp_activate_dev fails.
# --------------------------------------------
#
diff -Nru a/sound/isa/als100.c b/sound/isa/als100.c
--- a/sound/isa/als100.c Tue Mar 25 21:45:03 2003
+++ b/sound/isa/als100.c Tue Mar 25 21:45:03 2003
@@ -151,6 +151,7 @@
err = pnp_activate_dev(pdev);
if (err < 0) {
printk(KERN_ERR PFX "AUDIO pnp configure failure\n");
+ kfree(cfg);
return err;
}
port[dev] = pnp_port_start(pdev, 0);
next prev parent reply other threads:[~2003-03-26 3:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-25 22:33 [PATCH] PnP Changes for 2.5.66 Adam Belay
2003-03-25 22:33 ` Adam Belay
2003-03-25 22:34 ` Adam Belay [this message]
2003-03-25 22:35 ` Adam Belay
2003-03-25 22:36 ` Adam Belay
2003-03-25 22:37 ` Adam Belay
2003-03-25 22:37 ` Adam Belay
-- strict thread matches above, loose matches on Subject: below --
2003-04-04 0:07 Adam Belay
2003-04-04 0:08 ` Adam Belay
2003-04-04 0:08 ` Adam Belay
2003-04-04 0:09 ` Adam Belay
2003-04-04 0:10 ` Adam Belay
2003-04-04 0:11 ` Adam Belay
2003-04-04 0:11 ` Adam Belay
2003-04-04 0:12 ` Adam Belay
2003-04-04 0:12 ` Adam Belay
2003-04-04 0:13 ` Adam Belay
2003-04-04 0:13 ` Adam Belay
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=20030325223426.GE1083@neo.rr.com \
--to=ambx1@neo.rr.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox