From: Samuel Ortiz <sameo@linux.intel.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Andres Salomon <dilinger@queued.net>
Subject: Re: linux-next: build warning after merge of the mfd tree
Date: Tue, 30 Nov 2010 11:02:40 +0100 [thread overview]
Message-ID: <20101130100239.GB11125@sortiz-mobl> (raw)
In-Reply-To: <20101129115257.9a78ad14.sfr@canb.auug.org.au>
Hi Stephen,
On Mon, Nov 29, 2010 at 11:52:57AM +1100, Stephen Rothwell wrote:
> Hi Samuel,
>
> After merging the mfd tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
>
> drivers/mfd/cs5535-mfd.c: In function 'cs5535_mfd_probe':
> drivers/mfd/cs5535-mfd.c:106: warning: format '%d' expects type 'int', but argument 3 has type 'long unsigned int'
>
> Introduced by commit a0d4503a044e67ac46adfe8f42eddefd2b60f85e ("mfd: Add
> cs5535-mfd driver for AMD Geode's CS5535/CS5536 support").
That should be fixed by now, thanks for the report.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
next prev parent reply other threads:[~2010-11-30 10:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-29 0:52 linux-next: build warning after merge of the mfd tree Stephen Rothwell
2010-11-30 4:44 ` [PATCH] cs5535-mfd: fix warning on x86-64 Andres Salomon
2010-11-30 10:01 ` Samuel Ortiz
2010-12-07 18:38 ` Andres Salomon
2010-12-09 11:49 ` Samuel Ortiz
2010-11-30 18:22 ` Randy Dunlap
2010-11-30 21:44 ` Andres Salomon
2010-11-30 21:54 ` [PATCH] cs5535-mfd: fix warning on x86-64 (v2) Andres Salomon
2010-11-30 22:36 ` Randy Dunlap
2010-11-30 10:02 ` Samuel Ortiz [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-07-07 2:44 linux-next: build warning after merge of the mfd tree Stephen Rothwell
[not found] <20190627151140.232a87e2@canb.auug.org.au>
2019-06-27 5:59 ` Keerthy
2019-07-02 8:49 ` Stephen Rothwell
2019-07-02 11:09 ` Lee Jones
2018-06-05 3:15 Stephen Rothwell
2018-06-05 6:55 ` Lee Jones
2017-11-30 0:35 Stephen Rothwell
2017-11-30 8:28 ` Lee Jones
2017-01-25 4:54 Stephen Rothwell
2017-01-25 8:13 ` Benjamin Gaignard
2013-07-03 5:56 Stephen Rothwell
2013-07-07 18:29 ` Sebastian Andrzej Siewior
2011-12-20 3:11 Stephen Rothwell
2010-03-03 5:22 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=20101130100239.GB11125@sortiz-mobl \
--to=sameo@linux.intel.com \
--cc=dilinger@queued.net \
--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 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).