From: Marcel Holtmann <marcel@holtmann.org>
To: Dan Carpenter <error27@gmail.com>
Cc: Alicke Xu <sxu@atheros.com>,
"Luis R. Rodriguez" <lrodriguez@atheros.com>,
Vikram Kandukuri <vikram.kandukuri@atheros.com>,
linux-bluetooth@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch] bluetooth: ath3k: add kfree() on error path
Date: Mon, 08 Feb 2010 08:00:52 +0000 [thread overview]
Message-ID: <1265616052.31341.256.camel@localhost.localdomain> (raw)
In-Reply-To: <20100208054317.GA10576@bicker>
Hi Dan,
> Add a couple kfree() calls on an error path.
>
> Signed-off-by: Dan Carpenter <error27@gmail.com>
>
> ---
> I only compile tested this one and it's obvoiusly low priority. Could it go into linux-next?
patch has been applied. Thanks.
Regards
Marcel
WARNING: multiple messages have this Message-ID (diff)
From: Marcel Holtmann <marcel@holtmann.org>
To: Dan Carpenter <error27@gmail.com>
Cc: Alicke Xu <sxu@atheros.com>,
"Luis R. Rodriguez" <lrodriguez@atheros.com>,
Vikram Kandukuri <vikram.kandukuri@atheros.com>,
linux-bluetooth@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch] bluetooth: ath3k: add kfree() on error path
Date: Mon, 08 Feb 2010 09:00:52 +0100 [thread overview]
Message-ID: <1265616052.31341.256.camel@localhost.localdomain> (raw)
In-Reply-To: <20100208054317.GA10576@bicker>
Hi Dan,
> Add a couple kfree() calls on an error path.
>
> Signed-off-by: Dan Carpenter <error27@gmail.com>
>
> ---
> I only compile tested this one and it's obvoiusly low priority. Could it go into linux-next?
patch has been applied. Thanks.
Regards
Marcel
next prev parent reply other threads:[~2010-02-08 8:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-08 5:43 [patch] bluetooth: ath3k: add kfree() on error path Dan Carpenter
2010-02-08 5:43 ` Dan Carpenter
2010-02-08 8:00 ` Marcel Holtmann [this message]
2010-02-08 8:00 ` 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=1265616052.31341.256.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--cc=error27@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=lrodriguez@atheros.com \
--cc=sxu@atheros.com \
--cc=vikram.kandukuri@atheros.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.