From: Jean Delvare <khali@linux-fr.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: linux-next: build warning after merge of the i2c tree
Date: Mon, 29 Mar 2010 15:21:55 +0200 [thread overview]
Message-ID: <20100329152155.056741d2@hyperion.delvare> (raw)
In-Reply-To: <20100329105439.1e474095.sfr@canb.auug.org.au>
Hi Stephen,
On Mon, 29 Mar 2010 10:54:39 +1100, Stephen Rothwell wrote:
> Hi Jean,
>
> After merging the ii2c tree, today's linux-next build (powerpc
> ppc64_defconfig) produced this warning:
>
> drivers/i2c/i2c-core.c:159: warning: 'i2c_legacy_suspend' defined but not used
> drivers/i2c/i2c-core.c:172: warning: 'i2c_legacy_resume' defined but not used
>
> Introduced by commit 592b0bd0324728fe0aca823951eba06a9494c2f9 ("i2c: Fix
> bus-level power management callbacks"). These routines are only called
> if CONFIG_PM_SLEEP is defined.
Err, sorry. I noticed the problem and fixed it some days ago, but
forgot to refresh the patch before pushing it to you. This is fixed
now, thanks for the notice.
--
Jean Delvare
next prev parent reply other threads:[~2010-03-29 13:22 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-28 23:54 linux-next: build warning after merge of the i2c tree Stephen Rothwell
2010-03-29 13:21 ` Jean Delvare [this message]
2010-03-29 14:12 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2021-08-18 6:29 Stephen Rothwell
2021-08-18 6:54 ` Jie Deng
2021-08-18 7:04 ` Stephen Rothwell
2021-08-18 7:13 ` Jie Deng
2019-08-02 3:21 Stephen Rothwell
2019-08-02 6:04 ` Uwe Kleine-König
2019-06-11 0:25 Stephen Rothwell
2019-06-12 8:19 ` Wolfram Sang
2019-06-12 11:02 ` Mauro Carvalho Chehab
2019-06-12 11:09 ` Wolfram Sang
2019-06-12 11:48 ` Mauro Carvalho Chehab
2019-06-12 12:04 ` Wolfram Sang
2019-06-12 12:32 ` Mauro Carvalho Chehab
2019-06-12 13:15 ` Stephen Rothwell
2019-06-12 13:24 ` Wolfram Sang
2017-06-05 1:11 Stephen Rothwell
2017-06-15 1:34 ` Stephen Rothwell
2017-06-15 7:02 ` Wolfram Sang
2017-06-15 8:48 ` Stephen Rothwell
2014-03-06 2:50 Stephen Rothwell
2010-02-17 0:38 Stephen Rothwell
2010-02-17 8:34 ` Jean Delvare
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=20100329152155.056741d2@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rjw@sisk.pl \
--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).