From: Kalle Valo <kvalo@codeaurora.org>
To: Insu Yun <wuninsu@gmail.com>
Cc: akarwar@marvell.com, nishants@marvell.com,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, taesoo@gatech.edu,
yeongjin.jang@gatech.edu, insu@gatech.edu, changwoo@gatech.edu,
Insu Yun <wuninsu@gmail.com>
Subject: Re: [v2] mwifiex: correctly handling kzalloc
Date: Thu, 7 Jan 2016 09:12:30 +0000 (UTC) [thread overview]
Message-ID: <20160107091230.C5B58605BF@smtp.codeaurora.org> (raw)
In-Reply-To: <1451491304-35251-1-git-send-email-wuninsu@gmail.com>
> Since kzalloc can be failed in memory pressure,
> it needs to be handled, otherwise NULL dereference could be happened
>
> Signed-off-by: Insu Yun <wuninsu@gmail.com>
Thanks, applied to wireless-drivers-next.git.
Kalle Valo
prev parent reply other threads:[~2016-01-07 9:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-30 16:01 [PATCH v2] mwifiex: correctly handling kzalloc Insu Yun
2016-01-07 9:12 ` Kalle Valo [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=20160107091230.C5B58605BF@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=akarwar@marvell.com \
--cc=changwoo@gatech.edu \
--cc=insu@gatech.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nishants@marvell.com \
--cc=taesoo@gatech.edu \
--cc=wuninsu@gmail.com \
--cc=yeongjin.jang@gatech.edu \
/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.