From: Grant Likely <grant.likely@secretlab.ca>
To: Danny Kukawka <danny.kukawka@bisect.de>
Cc: Danny Kukawka <dkukawka@suse.de>,
Jiri Kosina <trivial@kernel.org>,
spi-devel-general@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] spi-topcliff-pch: fix -Wuninitialized warning
Date: Fri, 09 Mar 2012 14:43:37 -0700 [thread overview]
Message-ID: <20120309214337.A06483E0880@localhost> (raw)
In-Reply-To: <1329230103-26465-1-git-send-email-danny.kukawka@bisect.de>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2500 bytes --]
On Tue, 14 Feb 2012 15:35:03 +0100, Danny Kukawka <danny.kukawka@bisect.de> wrote:
> Fix for:
> drivers/spi/spi-topcliff-pch.c: In function ‘pch_spi_handler_sub’:
> drivers/spi/spi-topcliff-pch.c:325:17: warning: ‘bpw_len’ may be
> used uninitialized in this function [-Wuninitialized]
> drivers/spi/spi-topcliff-pch.c:325:42: warning: ‘rx_index’ may be
> used uninitialized in this function [-Wuninitialized]
> drivers/spi/spi-topcliff-pch.c:325:42: warning: ‘tx_index’ may be
> used uninitialized in this function [-Wuninitialized]
>
> Move usage of tx_index, rx_index and bpw_len into the same
> block as where they are set to prevent uninitialized usage.
>
> v2: instead of init variables with 0 move the whole block
>
> Signed-off-by: Danny Kukawka <danny.kukawka@bisect.de>
Applied, thanks
g.
> ---
> drivers/spi/spi-topcliff-pch.c | 33 +++++++++++++++----------------
> 1 files changed, 17 insertions(+), 16 deletions(-)
>
> diff --git a/drivers/spi/spi-topcliff-pch.c b/drivers/spi/spi-topcliff-pch.c
> index 10182eb..1107469 100644
> --- a/drivers/spi/spi-topcliff-pch.c
> +++ b/drivers/spi/spi-topcliff-pch.c
> @@ -318,22 +318,23 @@ static void pch_spi_handler_sub(struct pch_spi_data *data, u32 reg_spsr_val,
> data->tx_index = tx_index;
> data->rx_index = rx_index;
>
> - }
> -
> - /* if transfer complete interrupt */
> - if (reg_spsr_val & SPSR_FI_BIT) {
> - if ((tx_index == bpw_len) && (rx_index == tx_index)) {
> - /* disable interrupts */
> - pch_spi_setclr_reg(data->master, PCH_SPCR, 0, PCH_ALL);
> -
> - /* transfer is completed;
> - inform pch_spi_process_messages */
> - data->transfer_complete = true;
> - data->transfer_active = false;
> - wake_up(&data->wait);
> - } else {
> - dev_err(&data->master->dev,
> - "%s : Transfer is not completed", __func__);
> + /* if transfer complete interrupt */
> + if (reg_spsr_val & SPSR_FI_BIT) {
> + if ((tx_index == bpw_len) && (rx_index == tx_index)) {
> + /* disable interrupts */
> + pch_spi_setclr_reg(data->master, PCH_SPCR, 0,
> + PCH_ALL);
> +
> + /* transfer is completed;
> + inform pch_spi_process_messages */
> + data->transfer_complete = true;
> + data->transfer_active = false;
> + wake_up(&data->wait);
> + } else {
> + dev_err(&data->master->dev,
> + "%s : Transfer is not completed",
> + __func__);
> + }
> }
> }
> }
> --
> 1.7.7.3
>
--
Grant Likely, B.Sc, P.Eng.
Secret Lab Technologies,Ltd.
prev parent reply other threads:[~2012-03-09 21:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-14 14:35 [PATCH v2] spi-topcliff-pch: fix -Wuninitialized warning Danny Kukawka
2012-03-09 21:43 ` Grant Likely [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=20120309214337.A06483E0880@localhost \
--to=grant.likely@secretlab.ca \
--cc=danny.kukawka@bisect.de \
--cc=dkukawka@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=spi-devel-general@lists.sourceforge.net \
--cc=trivial@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox