From: Antoine Reversat <a.reversat@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: bugme-daemon@bugzilla.kernel.org, netdev@vger.kernel.org,
Patrick McHardy <kaber@trash.net>
Subject: Re: [Bugme-new] [Bug 37172] New: Enabling 802.1q vlan causes some packets to be received with a vlan id of 64
Date: Tue, 14 Jun 2011 09:31:52 -0400 [thread overview]
Message-ID: <BANLkTi=Omr+oe3nMiqVeS+8tiSJnxONbhQ@mail.gmail.com> (raw)
In-Reply-To: <20110613164355.c4f7b7b2.akpm@linux-foundation.org>
On Mon, Jun 13, 2011 at 7:43 PM, Andrew Morton
<akpm@linux-foundation.org> wrote:
>
> From which kernel version did we regress? Was 2.6.38 OK?
I can confirm this bug is present in 2.6.38.6
I'll try and see if I can reproduce it on a 2.6.37
next prev parent reply other threads:[~2011-06-14 13:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-37172-10286@https.bugzilla.kernel.org/>
2011-06-13 23:43 ` [Bugme-new] [Bug 37172] New: Enabling 802.1q vlan causes some packets to be received with a vlan id of 64 Andrew Morton
2011-06-14 13:31 ` Antoine Reversat [this message]
2011-06-15 16:13 ` Antoine Reversat
2011-06-15 16:57 ` Antoine Reversat
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='BANLkTi=Omr+oe3nMiqVeS+8tiSJnxONbhQ@mail.gmail.com' \
--to=a.reversat@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=kaber@trash.net \
--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).