From: patchwork-bot+linux-arm-msm@kernel.org
To: =?utf-8?b?Q2FybCBZaW4o5q635byg5oiQKSA8Y2FybC55aW5AcXVlY3RlbC5jb20+?=@ci.codeaurora.org
Cc: linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v2] bus: mhi: core: Fix null pointer access when parsing MHI configuration
Date: Tue, 29 Dec 2020 20:15:30 +0000 [thread overview]
Message-ID: <160927293060.13751.3283185144981186265.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201102122710.23406-1-carl.yin@quectel.com>
Hello:
This patch was applied to qcom/linux.git (refs/heads/for-next):
On Mon, 2 Nov 2020 20:27:10 +0800 you wrote:
> From: "carl.yin" <carl.yin@quectel.com>
>
> Functions parse_ev_cfg() and parse_ch_cfg() access mhi_cntrl->mhi_dev
> before it is set in function mhi_register_controller(),
> use cntrl_dev instead of mhi_dev.
>
> Fixes: 0cbf260820fa ("bus: mhi: core: Add support for registering MHI controllers")
> Signed-off-by: carl.yin <carl.yin@quectel.com>
> Reviewed-by: Bhaumik Bhatt <bbhatt@codeaurora.org>
>
> [...]
Here is the summary with links:
- [v2] bus: mhi: core: Fix null pointer access when parsing MHI configuration
https://git.kernel.org/qcom/c/f4d0b39c8425
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2020-12-29 20:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 12:27 [PATCH v2] bus: mhi: core: Fix null pointer access when parsing MHI configuration carl.yin
2020-11-03 22:05 ` Hemant Kumar
2020-11-05 16:05 ` Manivannan Sadhasivam
2020-11-09 12:01 ` Manivannan Sadhasivam
2020-12-29 20:15 ` patchwork-bot+linux-arm-msm [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=160927293060.13751.3283185144981186265.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-arm-msm@kernel.org \
--cc==?utf-8?b?Q2FybCBZaW4o5q635byg5oiQKSA8Y2FybC55aW5AcXVlY3RlbC5jb20+?=@ci.codeaurora.org \
--cc=linux-arm-msm@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 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.