From: "Sivakumar Subramani" <Sivakumar.Subramani@neterion.com>
To: "Jeff Garzik" <jeff@garzik.org>, <surya.prabhakar@wipro.com>
Cc: <mikep@linuxtr.net>, <netdev@vger.kernel.org>,
<linux-tr@linuxtr.net>,
"Linux Kernel" <linux-kernel@vger.kernel.org>,
"kernel-janitors" <kernel-janitors@lists.osdl.org>
Subject: RE: drivers/net/tokenring/3c359.c
Date: Thu, 16 Aug 2007 02:43:11 -0400 [thread overview]
Message-ID: <78C9135A3D2ECE4B8162EBDCE82CAD77020EEEC6@nekter> (raw)
In-Reply-To: <46C14297.1050800@garzik.org>
What exactly the difference between kzalloc and kcalloc? From the
definition, I could see that kcalloc should be used for array
allocation. But I could see kzalloc is used for allocation arrays as in
the below patch.
Any coding standard (or) developers can use kzalloc and kcalloc as per
their coding practice??
Thanks,
~Siva
-----Original Message-----
From: netdev-owner@vger.kernel.org [mailto:netdev-owner@vger.kernel.org]
On Behalf Of Jeff Garzik
Sent: Tuesday, August 14, 2007 11:20 AM
To: surya.prabhakar@wipro.com
Cc: mikep@linuxtr.net; netdev@vger.kernel.org; linux-tr@linuxtr.net;
Linux Kernel; kernel-janitors
Subject: Re: drivers/net/tokenring/3c359.c
Surya Prabhakar N wrote:
> Hi,
> Replacing kmalloc with kzalloc and cleaning up memset in
> drivers/net/tokenring/3c359.c
>
>
> Signed-off-by: Surya Prabhakar <surya.prabhakar@wipro.com>
applied
-
To unsubscribe from this list: send the line "unsubscribe netdev" in the
body of a message to majordomo@vger.kernel.org More majordomo info at
http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2007-08-16 6:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-13 10:13 drivers/net/tokenring/3c359.c Surya Prabhakar N
2007-08-13 13:59 ` drivers/net/tokenring/3c359.c Alan Cox
2007-08-14 5:50 ` drivers/net/tokenring/3c359.c Jeff Garzik
2007-08-16 6:43 ` Sivakumar Subramani [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=78C9135A3D2ECE4B8162EBDCE82CAD77020EEEC6@nekter \
--to=sivakumar.subramani@neterion.com \
--cc=jeff@garzik.org \
--cc=kernel-janitors@lists.osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tr@linuxtr.net \
--cc=mikep@linuxtr.net \
--cc=netdev@vger.kernel.org \
--cc=surya.prabhakar@wipro.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