From: David Miller <davem@davemloft.net>
To: harvey.harrison@gmail.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] net: ip_sockglue.c add static, annotate ports' endianness
Date: Thu, 20 Nov 2008 01:54:36 -0800 (PST) [thread overview]
Message-ID: <20081120.015436.15790123.davem@davemloft.net> (raw)
In-Reply-To: <1227039841.13182.1.camel@brick>
From: Harvey Harrison <harvey.harrison@gmail.com>
Date: Tue, 18 Nov 2008 12:24:01 -0800
> Fixes sparse warnings:
> net/ipv4/ip_sockglue.c:146:15: warning: incorrect type in assignment (different base types)
> net/ipv4/ip_sockglue.c:146:15: expected restricted __be16 [assigned] [usertype] sin_port
> net/ipv4/ip_sockglue.c:146:15: got unsigned short [unsigned] [short] [usertype] <noident>
> net/ipv4/ip_sockglue.c:130:6: warning: symbol 'ip_cmsg_recv_dstaddr' was not declared. Should it be static?
>
> Signed-off-by: Harvey Harrison <harvey.harrison@gmail.com>
> ---
> These are new warnings between next-20081117 and next-20081118
Applied, thanks.
prev parent reply other threads:[~2008-11-20 9:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-18 20:24 [PATCH] net: ip_sockglue.c add static, annotate ports' endianness Harvey Harrison
2008-11-20 9:54 ` David Miller [this message]
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=20081120.015436.15790123.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=harvey.harrison@gmail.com \
--cc=netdev@vger.kernel.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).