From: Willy Tarreau <w@1wt.eu>
To: zhuyj <zyjzyj2000@gmail.com>
Cc: "Yang, Zhangle \(Eric\)" <Zhangle.Yang@windriver.com>,
netdev@vger.kernel.org, richardcochran@gmail.com,
linuxppc-dev@lists.ozlabs.org, guang.yang@windriver.com,
linux-kernel@vger.kernel.org, yongjun_wei@trendmicro.com.cn,
sandeep.kumar@freescale.com,
Claudiu Manoil <claudiu.manoil@freescale.com>,
"Tao, Yue" <Yue.Tao@windriver.com>,
joe@perches.com, festevam@gmail.com, clarocq@gmail.com
Subject: Re: on kernel 2.6.34.15, vlan and raw packets can not be received with gfar-enet nic
Date: Thu, 3 Apr 2014 12:21:36 +0200 [thread overview]
Message-ID: <20140403102136.GF16158@1wt.eu> (raw)
In-Reply-To: <533D34BD.900@gmail.com>
On Thu, Apr 03, 2014 at 06:15:25PM +0800, zhuyj wrote:
> Hi, Willy
>
> I made a new patch. In long commit message, I inserted the equivalent
> mainline commit
> about this feature. Maybe it is better. Now this patch is in the
> attachment. Please check
> and merge it into kernel 2.6.32.62.
Sure, it's much better this way.
Thanks!
Willy
WARNING: multiple messages have this Message-ID (diff)
From: Willy Tarreau <w@1wt.eu>
To: zhuyj <zyjzyj2000@gmail.com>
Cc: sandeep.kumar@freescale.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, "Tao, Yue" <Yue.Tao@windriver.com>,
"Yang, Zhangle (Eric)" <Zhangle.Yang@windriver.com>,
guang.yang@windriver.com, joe@perches.com, festevam@gmail.com,
linuxppc-dev@lists.ozlabs.org, richardcochran@gmail.com,
clarocq@gmail.com, yongjun_wei@trendmicro.com.cn,
Claudiu Manoil <claudiu.manoil@freescale.com>
Subject: Re: on kernel 2.6.34.15, vlan and raw packets can not be received with gfar-enet nic
Date: Thu, 3 Apr 2014 12:21:36 +0200 [thread overview]
Message-ID: <20140403102136.GF16158@1wt.eu> (raw)
In-Reply-To: <533D34BD.900@gmail.com>
On Thu, Apr 03, 2014 at 06:15:25PM +0800, zhuyj wrote:
> Hi, Willy
>
> I made a new patch. In long commit message, I inserted the equivalent
> mainline commit
> about this feature. Maybe it is better. Now this patch is in the
> attachment. Please check
> and merge it into kernel 2.6.32.62.
Sure, it's much better this way.
Thanks!
Willy
next prev parent reply other threads:[~2014-04-03 10:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-25 5:08 on kernel 2.6.34.15, vlan and raw packets can not be received with gfar-enet nic zhuyj
2014-04-03 9:11 ` zhuyj
2014-04-03 9:11 ` zhuyj
2014-04-03 9:27 ` Willy Tarreau
2014-04-03 9:27 ` Willy Tarreau
2014-04-03 9:27 ` Willy Tarreau
2014-04-03 9:57 ` zhuyj
2014-04-03 9:57 ` zhuyj
2014-04-03 9:57 ` zhuyj
2014-04-03 10:01 ` Willy Tarreau
2014-04-03 10:01 ` Willy Tarreau
2014-04-03 10:01 ` Willy Tarreau
2014-04-03 10:18 ` zhuyj
2014-04-03 10:18 ` zhuyj
2014-04-03 10:18 ` zhuyj
2014-04-03 10:15 ` zhuyj
2014-04-03 10:15 ` zhuyj
2014-04-03 10:15 ` zhuyj
2014-04-03 10:21 ` Willy Tarreau [this message]
2014-04-03 10:21 ` Willy Tarreau
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=20140403102136.GF16158@1wt.eu \
--to=w@1wt.eu \
--cc=Yue.Tao@windriver.com \
--cc=Zhangle.Yang@windriver.com \
--cc=clarocq@gmail.com \
--cc=claudiu.manoil@freescale.com \
--cc=festevam@gmail.com \
--cc=guang.yang@windriver.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=sandeep.kumar@freescale.com \
--cc=yongjun_wei@trendmicro.com.cn \
--cc=zyjzyj2000@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.