From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Yangtao Li <tiny.windzz@gmail.com>
Subject: linux-next: build warning after merge of the clockevents tree
Date: Mon, 6 Jan 2020 13:37:16 +1100 [thread overview]
Message-ID: <20200106133716.62ea3548@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 597 bytes --]
Hi all,
After merging the clockevents tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:
drivers/clocksource/timer-ti-dm.c: In function 'omap_dm_timer_probe':
drivers/clocksource/timer-ti-dm.c:798:13: warning: 'timer' may be used uninitialized in this function [-Wmaybe-uninitialized]
798 | timer->irq = platform_get_irq(pdev, 0);
| ~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~
Introduced by commit
8c82723414d5 ("clocksource/drivers/timer-ti-dm: Switch to platform_get_irq")
This is not a false positive ...
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2020-01-06 2:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-06 2:37 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-08-14 1:16 linux-next: build warning after merge of the clockevents tree Stephen Rothwell
2025-07-16 6:08 Stephen Rothwell
[not found] ` <CAKnoXLynCY8dAe8k+ttTVpN2U49_-DyQFU7t1BRk-x74tfJ78Q@mail.gmail.com>
2025-07-18 22:08 ` Stephen Rothwell
2025-07-29 1:40 ` Stephen Rothwell
2025-07-30 12:22 ` Daniel Lezcano
2025-07-30 14:26 ` Stephen Rothwell
2014-01-16 4:03 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=20200106133716.62ea3548@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=tiny.windzz@gmail.com \
/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