From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Jiri Bohac <jbohac@suse.cz>
Subject: linux-next: build warning after merge of the origin tree
Date: Mon, 14 May 2012 10:44:52 +1000 [thread overview]
Message-ID: <20120514104452.2411b761e8f98076d1ae88ee@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 912 bytes --]
Hi Dave,
Buildinf Linus' tree, today's linux-next build (powerpc ppc64_defconfig)
produced these warnings:
drivers/net/bonding/bond_main.c: In function 'bond_handle_frame':
drivers/net/bonding/bond_main.c:1463:13: warning: assignment from incompatible pointer type [enabled by default]
drivers/net/bonding/bond_main.c: In function 'bond_open':
drivers/net/bonding/bond_main.c:3441:21: warning: assignment from incompatible pointer type [enabled by default]
drivers/net/bonding/bond_main.c:3448:20: warning: assignment from incompatible pointer type [enabled by default]
Introduced by commit 13a8e0c8cdb4 ("bonding: don't increase rx_dropped
after processing LACPDUs"). recv-probe in struct bonding is a function
returning void, but the local variable it assigned to/from has been
changed to a function returning int ...
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2012-05-14 0:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-14 0:44 Stephen Rothwell [this message]
2012-05-14 3:00 ` linux-next: build warning after merge of the origin tree David Miller
2019-11-27 20:59 Stephen Rothwell
2019-11-28 8:11 ` Linus Walleij
2021-01-06 22:05 Stephen Rothwell
2021-01-06 22:23 ` Johannes Berg
2021-01-06 22:44 ` Stephen Rothwell
2021-01-06 22:46 ` Johannes Berg
2021-01-06 23:20 ` Stephen Rothwell
2022-01-17 0:45 Stephen Rothwell
2022-01-17 1:27 ` Suren Baghdasaryan
2022-01-17 2:24 ` Stephen Rothwell
2022-01-17 22:01 ` Andrew Morton
2024-03-25 1:17 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=20120514104452.2411b761e8f98076d1ae88ee@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=davem@davemloft.net \
--cc=jbohac@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=torvalds@linux-foundation.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).