From: Al Viro <viro@ftp.linux.org.uk>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: ctindel@users.sourceforge.net, Jay Vosburgh <fubar@us.ibm.com>,
bonding-devel@lists.sourceforge.net, netdev@vger.kernel.org
Subject: Re: [PATCH] bonding: fix sparse warnings
Date: Thu, 11 May 2006 00:22:03 +0100 [thread overview]
Message-ID: <20060510232203.GK27946@ftp.linux.org.uk> (raw)
In-Reply-To: <20060510161405.4ded4250@localhost.localdomain>
On Wed, May 10, 2006 at 04:14:05PM -0700, Stephen Hemminger wrote:
> Fix warning from sparse in bonding code about "incorrect type in assignment"
*snerk*
Only if you are building without -Wcast-to-as. It _is_ incorrect type in
assignment. And the real fix is to expand the call, killing set_fs()
in there.
next prev parent reply other threads:[~2006-05-10 23:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-10 23:14 [PATCH] bonding: fix sparse warnings Stephen Hemminger
2006-05-10 23:22 ` Al Viro [this message]
2006-05-11 3:45 ` Stephen Hemminger
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=20060510232203.GK27946@ftp.linux.org.uk \
--to=viro@ftp.linux.org.uk \
--cc=bonding-devel@lists.sourceforge.net \
--cc=ctindel@users.sourceforge.net \
--cc=fubar@us.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@osdl.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).