From: Chris Lew <clew@codeaurora.org>
To: Arun Kumar Neelakantam <aneela@codeaurora.org>,
ohad@wizery.com, bjorn.andersson@linaro.org,
sricharan@codeaurora.org
Cc: linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rpmsg: glink: Initialize the "intent_req_comp" completion variable
Date: Fri, 27 Oct 2017 17:33:04 -0700 [thread overview]
Message-ID: <643ce1e4-8bb8-b7dd-6570-7a26cb6e42fb@codeaurora.org> (raw)
In-Reply-To: <1509101152-1340-1-git-send-email-aneela@codeaurora.org>
On 10/27/2017 3:45 AM, Arun Kumar Neelakantam wrote:
> The "intent_req_comp" variable is used without initialization which
> results in NULL pointer derefernce in qcom_glink_request_intent().
>
Typo on dereference.
Thanks,
Chris
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
prev parent reply other threads:[~2017-10-28 0:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-27 10:45 [PATCH] rpmsg: glink: Initialize the "intent_req_comp" completion variable Arun Kumar Neelakantam
2017-10-28 0:33 ` Chris Lew [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=643ce1e4-8bb8-b7dd-6570-7a26cb6e42fb@codeaurora.org \
--to=clew@codeaurora.org \
--cc=aneela@codeaurora.org \
--cc=bjorn.andersson@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=ohad@wizery.com \
--cc=sricharan@codeaurora.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