linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	abdoulaye berthe <berthe.ab@gmail.com>
Subject: linux-next: build warnings after merge of the gpio tree
Date: Wed, 23 Jul 2014 18:45:07 +1000	[thread overview]
Message-ID: <20140723184507.30c4b211@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 706 bytes --]

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@canb.auug.org.au

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

             reply	other threads:[~2014-07-23  8:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-23  8:45 Stephen Rothwell [this message]
2014-07-23  8:46 ` linux-next: build warnings after merge of the gpio tree Linus Walleij
2017-11-03  5:37 Stephen Rothwell
2017-11-09  3:51 ` Stephen Rothwell
2017-11-09  7:42   ` Linus Walleij
2017-11-09 14:37     ` Rob Herring
2017-11-15 22:42       ` Stephen Rothwell
2017-11-15 23:12         ` Rob Herring
2017-11-15 23:39           ` Stephen Rothwell
2017-12-05 22:48           ` Stephen Rothwell
2017-12-06 20:51             ` Rob Herring
2017-12-07 15:10               ` Arnd Bergmann

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=20140723184507.30c4b211@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=berthe.ab@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@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 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).