From: "Pekka Enberg" <penberg@cs.helsinki.fi>
To: "Panagiotis Issaris" <takis@gna.org>
Cc: "Daniel K." <daniel@cluded.net>,
"Panagiotis Issaris" <takis@lumumba.uhasselt.be>,
linux-kernel@vger.kernel.org, len.brown@intel.com,
chas@cmf.nrl.navy.mil, miquel@df.uba.ar, kkeil@suse.de,
benh@kernel.crashing.org, video4linux-list@redhat.com,
rmk+mmc@arm.linux.org.uk, Neela.Kolli@engenio.com,
jgarzik@pobox.com, vandrove@vc.cvut.cz, adaplas@pol.net,
thomas@winischhofer.net, weissg@vienna.at, philb@gnu.org,
linux-pcmcia@lists.infradead.org, jkmaline@cc.hut.fi,
paulus@samba.org
Subject: Re: Re: [PATCH] drivers: Conversions from kmalloc+memset to k(z|c)alloc.
Date: Thu, 20 Jul 2006 20:49:08 +0300 [thread overview]
Message-ID: <84144f020607201049g1391d3f4qfdb6f4a0821a5be8@mail.gmail.com> (raw)
In-Reply-To: <1153416317.11873.22.camel@hemera>
On 7/20/06, Panagiotis Issaris <takis@gna.org> wrote:
> I figured someone might want to add extra code in f.e. RIOGetCmddBlk to
> be able to debug/modify memory allocation behavior for the RIO driver
> only. It does look a bit messy though. So I've updated it in my updated
> patch.
Yes, we have people adding those and I keep trying to get rid of them
;-). With Al Viro's slab memory leak tracking patches in-tree and
Catalin's kmemleak on the way, there really is no excuse adding new
ones.
next prev parent reply other threads:[~2006-07-20 17:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-19 0:46 Panagiotis Issaris
2006-07-19 0:59 ` Alexey Dobriyan
2006-07-19 1:38 ` Panagiotis Issaris
2006-07-19 2:40 ` Daniel K.
2006-07-19 8:38 ` Pekka Enberg
2006-07-20 17:25 ` Panagiotis Issaris
2006-07-20 17:49 ` Pekka Enberg [this message]
2006-07-19 12:17 ` Antonino A. Daplas
2006-07-19 12:52 ` Paul Mackerras
2006-07-19 13:53 ` Pekka Enberg
2006-07-19 13:53 ` Paulo Marques
2006-07-20 18:03 ` Panagiotis Issaris
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=84144f020607201049g1391d3f4qfdb6f4a0821a5be8@mail.gmail.com \
--to=penberg@cs.helsinki.fi \
--cc=Neela.Kolli@engenio.com \
--cc=adaplas@pol.net \
--cc=benh@kernel.crashing.org \
--cc=chas@cmf.nrl.navy.mil \
--cc=daniel@cluded.net \
--cc=jgarzik@pobox.com \
--cc=jkmaline@cc.hut.fi \
--cc=kkeil@suse.de \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pcmcia@lists.infradead.org \
--cc=miquel@df.uba.ar \
--cc=paulus@samba.org \
--cc=philb@gnu.org \
--cc=rmk+mmc@arm.linux.org.uk \
--cc=takis@gna.org \
--cc=takis@lumumba.uhasselt.be \
--cc=thomas@winischhofer.net \
--cc=vandrove@vc.cvut.cz \
--cc=video4linux-list@redhat.com \
--cc=weissg@vienna.at \
/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®