From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Aishwarya Pant <aishpant@gmail.com>
Cc: Stephen Warren <swarren@wwwdotorg.org>,
Lee Jones <lee@kernel.org>, Eric Anholt <eric@anholt.net>,
Florian Fainelli <f.fainelli@gmail.com>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
bcm-kernel-feedback-list@broadcom.com,
outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] [PATCH v2] staging: bcm2835-camera: replace kmalloc with kzalloc
Date: Mon, 6 Mar 2017 13:53:07 +0100 [thread overview]
Message-ID: <20170306125307.GB26115@kroah.com> (raw)
In-Reply-To: <20170306072136.GA19014@aishwarya>
On Mon, Mar 06, 2017 at 12:51:36PM +0530, Aishwarya Pant wrote:
> This patch replaces two instances of kmalloc and memset with kzalloc
> and refactors function get_msg_context(..)
What did you refactor? Why do two things at once?
>
> Signed-off-by: Aishwarya Pant <aishpant@gmail.com>
>
> ---
> Changes in v2:
> - Return out of memory error number when kzalloc fails
> - Refactor get_msg_context
>
> drivers/staging/vc04_services/bcm2835-camera/mmal-vchiq.c | 13 +++++--------
> 1 file changed, 5 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/staging/vc04_services/bcm2835-camera/mmal-vchiq.c b/drivers/staging/vc04_services/bcm2835-camera/mmal-vchiq.c
> index 0f96ac8..87d7681 100644
> --- a/drivers/staging/vc04_services/bcm2835-camera/mmal-vchiq.c
> +++ b/drivers/staging/vc04_services/bcm2835-camera/mmal-vchiq.c
> @@ -166,13 +166,9 @@ struct vchiq_mmal_instance {
> static struct mmal_msg_context *get_msg_context(struct vchiq_mmal_instance
> *instance)
> {
> - struct mmal_msg_context *msg_context;
> -
> - /* todo: should this be allocated from a pool to avoid kmalloc */
> - msg_context = kmalloc(sizeof(*msg_context), GFP_KERNEL);
> - memset(msg_context, 0, sizeof(*msg_context));
> + /* todo: should this be allocated from a pool to avoid kzalloc */
> + return kzalloc(sizeof(*msg_context), GFP_KERNEL);
Why is this function even needed anymore? Why not just call kzalloc()
instead of this one?
thanks,
greg k-h
prev parent reply other threads:[~2017-03-06 12:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-06 7:21 [PATCH v2] staging: bcm2835-camera: replace kmalloc with kzalloc Aishwarya Pant
2017-03-06 12:53 ` Greg Kroah-Hartman [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=20170306125307.GB26115@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=aishpant@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=eric@anholt.net \
--cc=f.fainelli@gmail.com \
--cc=lee@kernel.org \
--cc=outreachy-kernel@googlegroups.com \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.com \
--cc=swarren@wwwdotorg.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.