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
Subject: Re: linux-next: build warnings after merge of the i2c tree
Date: Mon, 21 Feb 2011 10:58:58 +0100 [thread overview]
Message-ID: <20110221105858.197cbf1d@endymion.delvare> (raw)
In-Reply-To: <20110221153522.8a0b29bf.sfr@canb.auug.org.au>
Hi Stephen,
On Mon, 21 Feb 2011 15:35:22 +1100, Stephen Rothwell wrote:
> Hi Jean,
>
> After merging the tip tree, today's linux-next build (powerpc
> ppc64_defconfig) produced these warnings:
>
> drivers/i2c/i2c-core.c: In function 'i2c_do_add_adapter':
> drivers/i2c/i2c-core.c:799: warning: 'attach_adapter' is deprecated (declared at include/linux/i2c.h:149)
> drivers/i2c/i2c-core.c:804: warning: 'attach_adapter' is deprecated (declared at include/linux/i2c.h:149)
> drivers/i2c/i2c-core.c: In function 'i2c_do_del_adapter':
> drivers/i2c/i2c-core.c:985: warning: 'detach_adapter' is deprecated (declared at include/linux/i2c.h:150)
> drivers/i2c/i2c-core.c:988: warning: 'detach_adapter' is deprecated (declared at include/linux/i2c.h:150)
>
> Introduced by commit 95529c656b97b08c7a92504f98650a229f03ae04 ("i2c:
> Deprecate i2c_driver.attach_adapter and .detach_adapter"). We normally
> fix up as many uses of an interface as possible before deprecating it ...
These are the core locations where the deprecated callbacks are called.
Ideally they would _not_ emit warnings, are these are legitimate and
can't be removed before all drivers relying on these callbacks have
been fixed. If there is a way to silent these warnings, please let me
know, as I don't know of any.
--
Jean Delvare
next prev parent reply other threads:[~2011-02-21 9:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-21 4:35 linux-next: build warnings after merge of the i2c tree Stephen Rothwell
2011-02-21 9:58 ` Jean Delvare [this message]
2011-02-22 6:17 ` Stephen Rothwell
2011-02-22 8:55 ` 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=20110221105858.197cbf1d@endymion.delvare \
--to=khali@linux-fr$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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