linux-kernel - linux-next: build warnings after merge of the gpio tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20140723184507.30c4b211@canb.auug.org.au>
Date:	Wed, 23 Jul 2014 18:45:07 +1000
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Linus Walleij <linus.walleij@...aro.org>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	abdoulaye berthe <berthe.ab@...il.com>
Subject: linux-next: build warnings after merge of the gpio tree

Hi Linus,

After merging the gpio tree, today's linux-next build (powerpc
allyesconfig) produced these warnings:

drivers/gpio/gpio-ucb1400.c: In function 'ucb1400_gpio_remove':
drivers/gpio/gpio-ucb1400.c:92:2: warning: ignoring return value of 'gpiochip_remove', declared with attribute warn_unused_result [-Wunused-result]
  gpiochip_remove(&ucb->gc);
  ^

And lots of similar ones.

Introduced by commit 9f5132ae82fd ("gpio: remove all usage of
gpio_remove retval in driver/gpio").

Maybe the __must_check attribute should be removed from the declaration
of the function before removing the retval checking ...

-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au

Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)