From: David Miller <davem@davemloft.net>
To: shhuiw@gmail.com
Cc: kaber@trash.net, netdev@vger.kernel.org
Subject: Re: [PATCH] vlan: cleanup the usage of *vlan in vlan_dev_hard_header
Date: Thu, 01 Aug 2013 13:12:30 -0700 (PDT) [thread overview]
Message-ID: <20130801.131230.25199405118866430.davem@davemloft.net> (raw)
In-Reply-To: <51F9FBCF.9060405@gmail.com>
From: Wang Sheng-Hui <shhuiw@gmail.com>
Date: Thu, 01 Aug 2013 14:10:23 +0800
> We can use vlan directly after we get the pointer at the beginning
> *vlan = vlan_dev_priv(dev)
> and do not use vlan_dev_priv(dev) to access its fields afterwards.
>
> Signed-off-by: Wang Sheng-Hui <shhuiw@gmail.com>
This patch was corrupted by your email client.
Please read Documentation/email-clients.txt to learn how to
fix this, send a test patch to yourself, and only when you
can successfully apply the patch you receive in that test email
should you repost your patch again here.
Thanks.
next prev parent reply other threads:[~2013-08-01 20:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-01 6:10 [PATCH] vlan: cleanup the usage of *vlan in vlan_dev_hard_header Wang Sheng-Hui
2013-08-01 20:12 ` David Miller [this message]
2013-08-01 23:58 ` Wang Sheng-Hui
2013-08-02 0:12 ` 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=20130801.131230.25199405118866430.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=shhuiw@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).