From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Cc: linux-kernel@vger.kernel.org, kernel-janitors@lists.osdl.org,
bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] bluetooth drivers : kmalloc to kzalloc conversion
Date: Mon, 18 Sep 2006 08:13:28 +0200 [thread overview]
Message-ID: <1158560008.30486.12.camel@localhost> (raw)
In-Reply-To: <6b4e42d10609171754q7c7335f9pfab703d6b746236b@mail.gmail.com>
Hi Om,
> Tested by compiling with $make allmodconfig; make
>
> Signed off by Om Narasimhan <om.turyx@gmail.com>
>
> drivers/bluetooth/bfusb.c | 2 +-
> drivers/bluetooth/hci_usb.c | 11 +++++------
> 2 files changed, 6 insertions(+), 7 deletions(-)
the kzalloc is suppose to replace a kmalloc followed by a memset
operation. It is not the case for these changes and so these changes
make no sense.
Regards
Marcel
prev parent reply other threads:[~2006-09-18 6:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-18 0:54 bluetooth drivers : kmalloc to kzalloc conversion Om Narasimhan
[not found] ` <200609172121.36247.dtor@insightbb.com>
2006-09-18 2:24 ` Om Narasimhan
2006-09-18 2:38 ` Dmitry Torokhov
2006-09-18 6:13 ` Marcel Holtmann [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=1158560008.30486.12.camel@localhost \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=kernel-janitors@lists.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