From: Deepak Saxena <dsaxena@plexity.net>
To: Jiri Slaby <lnx4us@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [I2C] kmalloc + memset -> kzalloc conversion
Date: Mon, 3 Oct 2005 12:27:14 -0700 [thread overview]
Message-ID: <20051003192714.GA3686@plexity.net> (raw)
In-Reply-To: <3888a5cd0510010432h52ede401g6fe34b7f93a3c342@mail.gmail.com>
On Oct 01 2005, at 13:32, Jiri Slaby was caught saying:
> On 10/1/05, Deepak Saxena <dsaxena@plexity.net> wrote:
> > + iface = (struct keywest_iface *) kzalloc(tsize, GFP_KERNEL);
> cast isn't needed
> > + if (!(smbuses = (void *)kzalloc(2*sizeof(struct nforce2_smbus),
> > GFP_KERNEL)))
> cast from (void*) to (void*)? No...
Agree...but I'm just doing kzalloc changes for now and if I started
cleaning every piece of ugly or bloated code in the kernel, I would
spend the rest of my life looking at drivers/ACPI.
~Deepak
--
Deepak Saxena - dsaxena@plexity.net - http://www.plexity.net
Even a stopped clock gives the right time twice a day.
prev parent reply other threads:[~2005-10-03 19:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-01 7:36 [PATCH] [I2C] kmalloc + memset -> kzalloc conversion Deepak Saxena
2005-10-01 11:32 ` Jiri Slaby
2005-10-03 19:27 ` Deepak Saxena [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=20051003192714.GA3686@plexity.net \
--to=dsaxena@plexity.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lnx4us@gmail.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;
as well as URLs for NNTP newsgroup(s).