From: Muli Ben-Yehuda <muli@il.ibm.com>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] OSS: replace kmalloc()+memset() combos with kzalloc()
Date: Mon, 18 Dec 2006 22:08:12 +0200 [thread overview]
Message-ID: <20061218200812.GF3548@rhun.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0612181447001.6439@localhost.localdomain>
On Mon, Dec 18, 2006 at 02:53:05PM -0500, Robert P. J. Day wrote:
>
> Replace kmalloc() + memset() pairs with the appropriate kzalloc()
> calls.
>
> Signed-off-by: Robert P. J. Day <rpjday@mindspring.com>
>
> ---
>
> i could have sworn i submitted this patch a while back but it
> doesn't seem to have been applied. it's possible it's still in the
> queue somewhere but it seems unlikely at this point.
The OSS subsystem doesn't have an overall maintainer, for patches like
this you should probably CC akpm (CC'd). Also, ack on the trident
bits.
Cheers,
Muli
prev parent reply other threads:[~2006-12-18 20:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-18 19:53 [PATCH] OSS: replace kmalloc()+memset() combos with kzalloc() Robert P. J. Day
2006-12-18 20:08 ` Muli Ben-Yehuda [this message]
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=20061218200812.GF3548@rhun.ibm.com \
--to=muli@il.ibm.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@mindspring.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