netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: jszhang@marvell.com
Cc: thomas.petazzoni@free-electrons.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, rmk+kernel@arm.linux.org.uk
Subject: Re: [PATCH] net: mvneta: fix trivial cut-off issue in mvneta_ethtool_update_stats
Date: Thu, 21 Jan 2016 12:04:16 -0800 (PST)	[thread overview]
Message-ID: <20160121.120416.2119682070903117194.davem@davemloft.net> (raw)
In-Reply-To: <1453278985-6433-1-git-send-email-jszhang@marvell.com>

From: Jisheng Zhang <jszhang@marvell.com>
Date: Wed, 20 Jan 2016 16:36:25 +0800

> When s->type is T_REG_64, the high 32bits are lost in val. This patch
> fixes this trivial issue.
> 
> Signed-off-by: Jisheng Zhang <jszhang@marvell.com>
> Fixes: 9b0cdefa4cd5 ("net: mvneta: add ethtool statistics")

Applied.

      reply	other threads:[~2016-01-21 20:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-20  8:36 [PATCH] net: mvneta: fix trivial cut-off issue in mvneta_ethtool_update_stats Jisheng Zhang
2016-01-21 20:04 ` 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=20160121.120416.2119682070903117194.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=jszhang@marvell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=rmk+kernel@arm.linux.org.uk \
    --cc=thomas.petazzoni@free-electrons.com \
    /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).