linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Linux Next Mailing List" <linux-next@vger.kernel.org>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Nuno Sá" <nuno.sa@analog.com>
Subject: Re: linux-next: build warning after merge of the hwmon-staging tree
Date: Mon, 10 Feb 2020 16:24:42 -0800	[thread overview]
Message-ID: <339eac27-8630-abf1-0202-f9e34193c2ff@roeck-us.net> (raw)
In-Reply-To: <20200211092328.34ba4b9e@canb.auug.org.au>

On 2/10/20 2:23 PM, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the hwmon-staging tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
> 
> drivers/hwmon/axi-fan-control.c: In function 'axi_fan_control_probe':
> drivers/hwmon/axi-fan-control.c:419:26: warning: 'res' may be used uninitialized in this function [-Wmaybe-uninitialized]
>    419 |   (unsigned long long)res->start, ctl->base);
>        |                          ^~
> 
> Introduced by commit
> 
>    690dd9ce04f6 ("hwmon: Support ADI Fan Control IP")
> 

Fixed up (res was actually leftover from an earlier patch version
and unused).

Guenter

  reply	other threads:[~2020-02-11  0:24 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-10 22:23 linux-next: build warning after merge of the hwmon-staging tree Stephen Rothwell
2020-02-11  0:24 ` Guenter Roeck [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-03-26  5:03 Stephen Rothwell
2023-12-12  3:12 Stephen Rothwell
2023-12-12  5:11 ` Guenter Roeck
2023-10-30  5:15 Stephen Rothwell
2022-08-31  5:30 Stephen Rothwell
2022-05-10 10:11 Stephen Rothwell
2022-05-10 10:47 ` Zev Weiss
2022-05-10 14:03   ` Guenter Roeck
2022-05-03  7:22 Stephen Rothwell
2022-05-03  7:34 ` Michael Walle
2022-05-03 13:08   ` Guenter Roeck
2022-02-10  7:51 Stephen Rothwell
2022-02-10  8:50 ` Lee Jones
2022-02-10 17:33   ` Guenter Roeck
2022-02-10 18:07     ` Lee Jones
2022-02-10 18:22       ` Guenter Roeck
2022-02-04  5:16 Stephen Rothwell
2022-02-04  5:25 ` Guenter Roeck
2021-12-20 11:31 Stephen Rothwell
2021-12-20  0:00 Stephen Rothwell
2021-06-10  0:21 Stephen Rothwell
2021-06-10  3:38 ` Guenter Roeck
2021-03-30  7:27 Stephen Rothwell
2021-03-30 10:38 ` Guenter Roeck
2021-03-30 20:25 ` Chris Packham
2021-03-30 20:55   ` Guenter Roeck
2021-03-12  3:50 Stephen Rothwell
2021-03-12  4:00 ` Chris Packham
2021-03-12  4:45   ` Stephen Rothwell
2021-01-29  7:03 Stephen Rothwell
2020-12-07  7:51 Stephen Rothwell
2020-11-30  0:56 Stephen Rothwell
2020-11-30  1:14 ` Paul Barker
2020-11-30 14:53   ` Guenter Roeck
2019-07-01  2:26 Stephen Rothwell
2019-06-06  0:34 Stephen Rothwell

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=339eac27-8630-abf1-0202-f9e34193c2ff@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=nuno.sa@analog.com \
    --cc=sfr@canb.auug.org.au \
    /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).