From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Sweta Bhatt <sweta.bhatt@einfochips.com>,
Roland Dreier <rolandd@cisco.com>,
Davide Rizzo <elpa.rizzo@gmail.com>,
Michael Hennerich <michael.hennerich@analog.com>,
Mike Frysinger <vapier@gentoo.org>,
Richard Purdie <rpurdie@linux.intel.com>,
Joseph Chan <JosephChan@via.com.tw>
Subject: Re: linux-next: build warnings from Linus' tree
Date: Thu, 28 Oct 2010 04:04:54 +0100 [thread overview]
Message-ID: <20101028030454.GB15103@sirena.org.uk> (raw)
In-Reply-To: <20101028112739.0f400818.sfr@canb.auug.org.au>
On Thu, Oct 28, 2010 at 11:27:39AM +1100, Stephen Rothwell wrote:
> While building Linus' tree, today's linux-next build (x86_64 allmodconfig)
> produced these warnings:
> sound/soc/soc-core.c: In function 'pmdown_time_set':
> sound/soc/soc-core.c:169: warning: ignoring return value of 'strict_strtol', declared with attribute warn_unused_result
Just cooked up a patch for this but due to timezone/travel on the part
of both myself and Liam it may not make get reviewed and into -next for
a little while.
next prev parent reply other threads:[~2010-10-28 3:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-28 0:27 linux-next: build warnings from Linus' tree Stephen Rothwell
2010-10-28 3:04 ` Mark Brown [this message]
2018-06-11 22:14 Stephen Rothwell
2018-11-14 4:54 ` Joel Stanley
2018-11-14 10:20 ` Michael Ellerman
2018-11-18 11:22 ` Alan Modra
2018-12-03 23:24 ` Joel Stanley
2018-08-19 22:13 Stephen Rothwell
2018-08-19 22:16 ` Stephen Rothwell
2018-08-19 22:40 ` Stephen Rothwell
2018-08-19 23:21 ` Linus Torvalds
2018-08-20 1:33 ` Adam Borowski
2018-08-20 2:53 ` Theodore Y. Ts'o
2018-08-20 0:02 ` Theodore Y. Ts'o
2018-08-20 17:47 ` Miguel Ojeda
2019-08-29 21:59 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=20101028030454.GB15103@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=JosephChan@via.com.tw \
--cc=akpm@linux-foundation.org \
--cc=elpa.rizzo@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=michael.hennerich@analog.com \
--cc=rolandd@cisco.com \
--cc=rpurdie@linux.intel.com \
--cc=sfr@canb.auug.org.au \
--cc=sweta.bhatt@einfochips.com \
--cc=vapier@gentoo.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).