From: Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com>
To: madalin.bucur@freescale.com
Cc: davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [PATCH] ipv4: fix 32b build
Date: Mon, 31 Aug 2015 18:27:16 +0530 [thread overview]
Message-ID: <55E44F2C.7020809@linux.vnet.ibm.com> (raw)
In-Reply-To: <1441025167-13740-1-git-send-email-madalin.bucur@freescale.com>
On 08/31/2015 06:16 PM, Madalin Bucur wrote:
> Address remaining issue after 80ec192.
>
> Signed-off-by: Madalin Bucur <madalin.bucur@freescale.com>
> ---
> net/ipv4/af_inet.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/net/ipv4/af_inet.c b/net/ipv4/af_inet.c
> index c2d0ebc..96773a2 100644
> --- a/net/ipv4/af_inet.c
> +++ b/net/ipv4/af_inet.c
> @@ -1496,7 +1496,7 @@ u64 snmp_fold_field64(void __percpu *mib, int offt, size_t syncp_offset)
> int cpu;
>
> for_each_possible_cpu(cpu) {
> - res += snmp_get_cpu_field(mib, cpu, offt, syncp_offset);
> + res += snmp_get_cpu_field64(mib, cpu, offt, syncp_offset);
> }
> return res;
> }
Thanks Madlin for catching this for 32bit.
next prev parent reply other threads:[~2015-08-31 12:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-31 12:46 [PATCH] ipv4: fix 32b build Madalin Bucur
2015-08-31 12:57 ` Raghavendra K T [this message]
2015-08-31 18:38 ` David Miller
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=55E44F2C.7020809@linux.vnet.ibm.com \
--to=raghavendra.kt@linux.vnet.ibm.com \
--cc=davem@davemloft.net \
--cc=madalin.bucur@freescale.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).