From: Stephen Hemminger <stephen@networkplumber.org>
To: roy.qing.li@gmail.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] vxlan: small improvements
Date: Thu, 16 Oct 2014 15:05:04 +0200 [thread overview]
Message-ID: <20141016150504.59db62b5@uryu.home.lan> (raw)
In-Reply-To: <1413450045-5008-1-git-send-email-roy.qing.li@gmail.com>
On Thu, 16 Oct 2014 17:00:44 +0800
roy.qing.li@gmail.com wrote:
> From: Li RongQing <roy.qing.li@gmail.com>
>
> 1. remove the dead codes, pr_fmt definition and vxlan_salt variable
> 2. pskb_may_pull() can change skb->data, so we have to reload eth in vxlan_xmit.
>
> Signed-off-by: Li RongQing <roy.qing.li@gmail.com>
You are doing 4 things in one patch.
The pr_fmt definition is standard way to identify where log messages orginate
next prev parent reply other threads:[~2014-10-16 13:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-16 9:00 [PATCH] vxlan: small improvements roy.qing.li
2014-10-16 13:05 ` Stephen Hemminger [this message]
2014-10-16 14:05 ` Eric Dumazet
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=20141016150504.59db62b5@uryu.home.lan \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.org \
--cc=roy.qing.li@gmail.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).