From: ebiederm@xmission.com (Eric W. Biederman)
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, greearb@candelatech.com, arnd@arndb.de,
kaber@trash.net, Daniel Lezcano <daniel.lezcano@free.fr>
Subject: Re: [PATCH] net: Handle gso packets in dev_forward_skb
Date: Mon, 28 Mar 2011 12:36:26 -0700 [thread overview]
Message-ID: <m1ei5rghqd.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <1301340048.2506.13.camel@edumazet-laptop> (Eric Dumazet's message of "Mon, 28 Mar 2011 21:20:48 +0200")
Eric Dumazet <eric.dumazet@gmail.com> writes:
> Le dimanche 27 mars 2011 à 18:09 -0700, David Miller a écrit :
>> From: ebiederm@xmission.com (Eric W. Biederman)
>> Date: Mon, 21 Mar 2011 15:00:56 -0700
>>
>> > Eric Dumazet <eric.dumazet@gmail.com> writes:
>> >
>> >> Hmm, did you follow http://patchwork.ozlabs.org/patch/86815/
>> >> discussion ?
>> >
>> > No. It seems I missed it, but I do have the same problem, and
>> > essentially the same fix.
>>
>> Can someone work on getting this straightened out and resubmit the
>> final patch so I can apply something?
>>
>
> Apparently Daniel is busy.
>
> I guess we can use Eric B. patch, then ?
That sounds good to me.
After reviewing the other thread to the best of my knowledge there are
no issues with the patch I submitted. At worst I am 4 bytes extra
permissive about the mtu because of the way that path handles vlan
headers and that isn't something my patch changed.
Eric
next prev parent reply other threads:[~2011-03-28 19:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 21:25 [PATCH] net: Handle gso packets in dev_forward_skb Eric W. Biederman
2011-03-21 21:42 ` Eric Dumazet
2011-03-21 22:00 ` Eric W. Biederman
2011-03-28 1:09 ` David Miller
2011-03-28 19:20 ` Eric Dumazet
2011-03-28 19:36 ` Eric W. Biederman [this message]
2011-03-29 12:54 ` Daniel Lezcano
2011-03-29 21:02 ` Eric W. Biederman
2011-03-30 7:06 ` 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=m1ei5rghqd.fsf@fess.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=arnd@arndb.de \
--cc=daniel.lezcano@free.fr \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=greearb@candelatech.com \
--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 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.