All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-arm-msm@kernel.org
To: Colin King <colin.king@canonical.com>
Cc: linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH][next] thermal: qcom: Fix comparison with uninitialized variable channels_available
Date: Mon, 01 Mar 2021 19:59:43 +0000	[thread overview]
Message-ID: <161462878370.6187.17593566565754405283.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210216151626.162996-1-colin.king@canonical.com>

Hello:

This patch was applied to qcom/linux.git (refs/heads/for-next):

On Tue, 16 Feb 2021 15:16:26 +0000 you wrote:
> From: Colin Ian King <colin.king@canonical.com>
> 
> Currently the check of chip->channels[i].channel is against an the
> uninitialized variable channels_available.  I believe the variable
> channels_available needs to be fetched first by the call to adc_tm5_read
> before the channels check. Fix the issue swapping the order of the
> channels check loop with the call to adc_tm5_read.
> 
> [...]

Here is the summary with links:
  - [next] thermal: qcom: Fix comparison with uninitialized variable channels_available
    https://git.kernel.org/qcom/c/74369d041a0a

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2021-03-01 20:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-16 15:16 [PATCH][next] thermal: qcom: Fix comparison with uninitialized variable channels_available Colin King
2021-02-18 20:39 ` [thermal: thermal/next] " thermal-bot for Colin Ian King
2021-03-01 19:59 ` 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=161462878370.6187.17593566565754405283.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-arm-msm@kernel.org \
    --cc=colin.king@canonical.com \
    --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.