From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Parag Warudkar <kernel-stuff@comcast.net>
Cc: Manfred Spraul <manfred@colorfullife.com>,
akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Document kfree and vfree NULL usage (resend)
Date: Mon, 06 Dec 2004 10:09:10 +0200 [thread overview]
Message-ID: <1102320551.10063.6.camel@localhost> (raw)
In-Reply-To: <200412051648.08283.kernel-stuff@comcast.net>
Hi Parag,
On Sun, 2004-12-05 at 16:48 -0500, Parag Warudkar wrote:
> I was not able to apply your patch which I copied from KMail - so
> looks like KMail is inserting some control chars.
>
> So here is what I did - I applied your patch to vmalloc.c manually
> and then modified vmalloc.c to include my changes. Attached is the new
> patch.
> If this doesn't work would you mind manually applying vfree() and
> vunmap() doc changes to your patch and submit?
I appreciate the help but please don't do this. You're creating more
work for me and confusion to the maintainers now. If Andrew already
picked up my patch, your new patch will not apply. If he didn't, he
cannot use your patch either because you left out the kfree() part
completely. Manfred said he would send a separate patch so please
respect that.
Andrew, please apply the original patch I sent and ignore the follow up
patches to this thread.
Pekka
next prev parent reply other threads:[~2004-12-06 8:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-03 19:48 [PATCH] Document kfree and vfree NULL usage (resend) Pekka Enberg
2004-12-05 15:33 ` Manfred Spraul
2004-12-05 16:05 ` Kernel Stuff
2004-12-05 16:59 ` Manfred Spraul
2004-12-05 17:44 ` Kernel Stuff
2004-12-05 17:57 ` Manfred Spraul
2004-12-05 18:12 ` Parag Warudkar
2004-12-05 20:29 ` Pekka Enberg
[not found] ` <200412051648.08283.kernel-stuff@comcast.net>
2004-12-06 8:09 ` Pekka Enberg [this message]
2004-12-05 20:21 ` Pekka Enberg
2004-12-05 20:38 ` Parag Warudkar
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=1102320551.10063.6.camel@localhost \
--to=penberg@cs.helsinki.fi \
--cc=akpm@osdl.org \
--cc=kernel-stuff@comcast.net \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox