From: Paulo Marques <pmarques@grupopie.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org
Subject: Re: [PATCH 2.6] 7/7 replace snd_kmalloc_strdup by kstrdup
Date: Tue, 01 Feb 2005 12:27:44 +0000 [thread overview]
Message-ID: <41FF75C0.6040602@grupopie.com> (raw)
In-Reply-To: <s5h651ch6lc.wl@alsa2.suse.de>
Takashi Iwai wrote:
> At Tue, 1 Feb 2005 03:28:46 +0000,
> "" <pmarques@grupopie.com> wrote:
>
>>[1 <text/plain; iso-8859-1 (quoted-printable)>]
>>
>>This patch removes the strdup implementation from the sound core
>>(snd_kmalloc_strdup), and updates it to use the kstrdup library function.
>>
>>Signed-off-by: Paulo Marques <pmarques@grupopie.com>
>
>
> This patch won't work properly if CONFIG_SND_DEBUG_MEMORY is set...
Humm.. compiles ok here.
I just rebuilt a vanilla 2.6.11-rc2-bk9 tree, applied the patches,
selected CONFIG_SND_DEBUG and CONFIG_SND_DEBUG_MEMORY, and it compiled
just fine.
I had already tested the patches with an allyesconfig, but tested it
anyway just to be sure.
Are you sure you also applied the first patch in the series that creates
the kstrdup library function? If you are, can you send me your .config
so that I can test it here?
--
Paulo Marques - www.grupopie.com
All that is necessary for the triumph of evil is that good men do nothing.
Edmund Burke (1729 - 1797)
next prev parent reply other threads:[~2005-02-01 12:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-01 3:28 [PATCH 2.6] 7/7 replace snd_kmalloc_strdup by kstrdup pmarques
2005-02-01 11:17 ` Takashi Iwai
2005-02-01 12:27 ` Paulo Marques [this message]
2005-02-01 12:32 ` Takashi Iwai
2005-02-01 13:07 ` Paulo Marques
2005-02-01 13:16 ` Takashi Iwai
2005-02-01 15:39 ` Paulo Marques
2005-02-01 16:39 ` Takashi Iwai
2005-02-01 17:15 ` Paulo Marques
2005-02-02 11:29 ` Takashi Iwai
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=41FF75C0.6040602@grupopie.com \
--to=pmarques@grupopie.com \
--cc=akpm@osdl.org \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.de \
/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