From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: mcarlson@broadcom.com, netdev@vger.kernel.org, andy@greyhouse.net
Subject: Re: [PATCH net-next 0/11] tg3: 5719, VLAN, and EEE bugfixes
Date: Tue, 25 Jan 2011 22:27:34 -0800 (PST) [thread overview]
Message-ID: <20110125.222734.189693738.davem@davemloft.net> (raw)
In-Reply-To: <1296022477.2633.16.camel@edumazet-laptop>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Wed, 26 Jan 2011 07:14:37 +0100
> I tested the vlan patch on my machine, and it solves the problem I had
> with linux-2.6
>
> I believe this particular patch should be net-2.6 material, not
> net-next-2.6
Agreed.
> (There is a small rejected hunk)
Matt, if you would send me a net-2.6 backport with your blessing
I'd appreciate it.
next prev parent reply other threads:[~2011-01-26 6:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-26 1:58 [PATCH net-next 0/11] tg3: 5719, VLAN, and EEE bugfixes Matt Carlson
2011-01-26 3:38 ` David Miller
2011-01-26 6:14 ` Eric Dumazet
2011-01-26 6:27 ` David Miller [this message]
2011-01-26 20:01 ` Matt Carlson
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=20110125.222734.189693738.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andy@greyhouse.net \
--cc=eric.dumazet@gmail.com \
--cc=mcarlson@broadcom.com \
--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).