From: Alexey Dobriyan <adobriyan@gmail.com>
To: Donald.Huang@ite.com.tw
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: iteraid.patch added to -mm tree
Date: Fri, 17 Jun 2005 03:47:39 -0700 [thread overview]
Message-ID: <b6fcc0a05061703472c19b7f2@mail.gmail.com> (raw)
In-Reply-To: <200506170053.j5H0rB6L009951@shell0.pdx.osdl.net>
On 6/16/05, akpm@osdl.org <akpm@osdl.org> wrote:
>
> The patch titled
>
> ITE RAID driver
>
> has been added to the -mm tree.
> +u8 IT8212GetChipStatus(uioctl_t * ioc)
> +{
> + pPhyDiskInfo = kmalloc(sizeof(PHYSICAL_DISK_STATUS) * 4, GFP_KERNEL);
> + if (pPhyDiskInfo == NULL) {
> + printk("IT8212GetChipStatus: error kmalloc for "
> + "PHYSCIAL_DISK_STATUS.\n");
> + return -ENOMEM;
> + }
> + memset(pPhyDiskInfo, 0, sizeof(PHYSICAL_DISK_STATUS));
kmalloc or memset is right wrt size?
Expect patches to fix sparse warnings, remove useless comments,
typedef horrors and other misc stuff in a day or so.
parent reply other threads:[~2005-06-17 10:47 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <200506170053.j5H0rB6L009951@shell0.pdx.osdl.net>]
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=b6fcc0a05061703472c19b7f2@mail.gmail.com \
--to=adobriyan@gmail.com \
--cc=Donald.Huang@ite.com.tw \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
/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