From: "Arend van Spriel" <arend@broadcom.com>
To: "Colin King" <colin.king@canonical.com>
Cc: "Franky (Zhenhui) Lin" <frankyl@broadcom.com>,
"John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] brcm80211: fix missing allocation failure check
Date: Mon, 10 Sep 2012 14:29:28 +0200 [thread overview]
Message-ID: <504DDD28.6020804@broadcom.com> (raw)
In-Reply-To: <1347267926-7118-1-git-send-email-colin.king@canonical.com>
On 09/10/2012 11:05 AM, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> Check for oobirq_entry allocation failure to avoid
> NULL pointer dereferencing.
Acked-by: Arend van Spriel <arend@broadcom.com>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
> drivers/net/wireless/brcm80211/brcmfmac/bcmsdh_sdmmc.c | 2 ++
> 1 file changed, 2 insertions(+)
Thanks.
Gr. AvS
prev parent reply other threads:[~2012-09-10 12:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-10 9:05 [PATCH] brcm80211: fix missing allocation failure check Colin King
2012-09-10 12:29 ` Arend van Spriel [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=504DDD28.6020804@broadcom.com \
--to=arend@broadcom.com \
--cc=colin.king@canonical.com \
--cc=frankyl@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).