From: David Miller <davem@davemloft.net>
To: zhangshengju@cmss.chinamobile.com
Cc: netdev@vger.kernel.org, dsa@cumulusnetworks.com
Subject: Re: [net-next] neigh: fix the loop index error in neigh dump
Date: Fri, 25 Nov 2016 20:17:03 -0500 (EST) [thread overview]
Message-ID: <20161125.201703.1849738894862872332.davem@davemloft.net> (raw)
In-Reply-To: <1479965109-14607-1-git-send-email-zhangshengju@cmss.chinamobile.com>
From: Zhang Shengju <zhangshengju@cmss.chinamobile.com>
Date: Thu, 24 Nov 2016 13:25:09 +0800
> Loop index in neigh dump function is not updated correctly under some
> circumstances, this patch will fix it.
>
> Signed-off-by: Zhang Shengju <zhangshengju@cmss.chinamobile.com>
If this bug is also in the 'net' tree you should target this patch
there.
Also, you must provide an appropriate "Fixes: " tag identifying
the commit which introduced this bug.
prev parent reply other threads:[~2016-11-26 1:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-24 5:25 [net-next] neigh: fix the loop index error in neigh dump Zhang Shengju
2016-11-26 1:17 ` 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=20161125.201703.1849738894862872332.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dsa@cumulusnetworks.com \
--cc=netdev@vger.kernel.org \
--cc=zhangshengju@cmss.chinamobile.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).