From: Takashi Iwai <tiwai@suse.de>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6/8] param: use free hook for charp
Date: Fri, 30 Oct 2009 11:14:43 +0100 [thread overview]
Message-ID: <s5hws2dyyr0.wl%tiwai@suse.de> (raw)
In-Reply-To: <20091022142342.14D378655F@mx2.suse.de>
Hi Rusty,
sorry for the delayed reply; I finally got back to work now.
At Fri, 23 Oct 2009 00:51:29 +1030,
Rusty Russell wrote:
>
>
> Instead of using a "I kmalloced this" flag, we keep track of the kmalloced
> strings and use that list to check if we need to kfree (in practice, the
> list is very short).
>
> This means that kparams can be const again.
>
> Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
This is indeed a simple solution! I like it.
thanks,
Takashi
parent reply other threads:[~2009-10-30 10:14 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20091022142342.14D378655F@mx2.suse.de>]
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=s5hws2dyyr0.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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
all inboxes | Powered by JetHome®