netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: WANG Cong <xiyou.wangcong@gmail.com>
To: netdev@vger.kernel.org
Subject: Re: [PATCH] vlan: fix typo in vlan_dev_hard_start_xmit()
Date: Wed, 1 Jun 2011 13:54:42 +0000 (UTC)	[thread overview]
Message-ID: <is5gb2$1h6$2@dough.gmane.org> (raw)
In-Reply-To: 4DE5FDFF.4000208@cn.fujitsu.com

On Wed, 01 Jun 2011 16:53:19 +0800, Wei Yongjun wrote:

> commit 4af429d29b341bb1735f04c2fb960178ed5d52e7 (vlan: lockless transmit
> path) have a typo in vlan_dev_hard_start_xmit(), using
> u64_stats_update_begin() to end the stat update, it should be
> u64_stats_update_end().
> 
> Signed-off-by: Wei Yongjun <yjwei@cn.fujitsu.com>

Yup, good catch!

Reviewed-by: WANG Cong <xiyou.wangcong@gmail.com>


  reply	other threads:[~2011-06-01 13:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-01  8:53 [PATCH] vlan: fix typo in vlan_dev_hard_start_xmit() Wei Yongjun
2011-06-01 13:54 ` WANG Cong [this message]
2011-06-01 15:07 ` Eric Dumazet
2011-06-02  4:09   ` 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='is5gb2$1h6$2@dough.gmane.org' \
    --to=xiyou.wangcong@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).