All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Jonathan Cameron <Jonathan.Cameron@huawei.com>,
	Krzysztof Kozlowski <krzk@kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the staging tree
Date: Wed, 9 Sep 2020 09:41:30 +0200	[thread overview]
Message-ID: <20200909074130.GB561485@kroah.com> (raw)
In-Reply-To: <20200909171621.28de7d12@canb.auug.org.au>

On Wed, Sep 09, 2020 at 05:16:21PM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the staging tree, today's linux-next build (arm
> multi_v7_defconfig) produced this warning:
> 
> drivers/iio/adc/stm32-adc-core.c: In function 'stm32_adc_core_switches_probe':
> drivers/iio/adc/stm32-adc-core.c:598:5: warning: ignoring return value of 'dev_err_probe' declared with attribute 'warn_unused_result' [-Wunused-result]
>   598 |     dev_err_probe(dev, ret, "can't get booster\n");
>       |     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 
> Introduced by commit
> 
>   ce30eeb613cb ("iio: adc: stm32: Simplify with dev_err_probe()")

Offending patch now dropped from the driver-core tree, thanks.

greg k-h

  reply	other threads:[~2020-09-09  7:41 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-09  7:16 linux-next: build warning after merge of the staging tree Stephen Rothwell
2020-09-09  7:41 ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-12-13  1:10 Stephen Rothwell
2019-08-26  6:24 Stephen Rothwell
2019-08-26  6:30 ` Greg KH
2019-08-26  8:38   ` Gao Xiang
2019-08-26  8:54     ` Gao Xiang
2019-08-26  9:43       ` Gao Xiang
2019-08-26  9:53         ` Gao Xiang
2019-08-26 11:13           ` Gao Xiang
2019-08-14  6:08 Stephen Rothwell
2019-08-14  7:42 ` Greg KH
2019-04-23  5:13 Stephen Rothwell
2018-11-08  2:33 Stephen Rothwell
2018-11-08 11:17 ` Greg KH
2018-09-03  2:06 Stephen Rothwell
2018-09-04  9:04 ` John Whitmore
2018-05-14  4:37 Stephen Rothwell
2018-01-16  2:45 Stephen Rothwell
2018-01-16  5:59 ` Greg KH
2018-01-16 10:47   ` Arnd Bergmann
2018-01-16 15:02     ` Greg KH
2017-01-20  4:36 Stephen Rothwell
2017-01-20  8:37 ` Greg KH
2017-01-20  9:18   ` Linus Walleij

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=20200909074130.GB561485@kroah.com \
    --to=greg@kroah.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.