From: "David S. Miller" <davem@redhat.com>
To: Ben Greear <greearb@candelatech.com>
Cc: vlan@candelatech.com, pavlic@de.ibm.com, netdev@oss.sgi.com
Subject: Re: FWD: setting skb->dev to vlan device in vlan_hwaccel_rx is wrong ...
Date: Tue, 19 Oct 2004 23:36:18 -0700 [thread overview]
Message-ID: <20041019233618.6fdcb01d.davem@redhat.com> (raw)
In-Reply-To: <41705CF2.9050303@candelatech.com>
On Fri, 15 Oct 2004 16:27:46 -0700
Ben Greear <greearb@candelatech.com> wrote:
> Dave, since you did the hw-accel work, what do you think of this patch?
I see no mention of what specific part of the "receive path"
depends upon the skb->dev being set to the real_dev and not
the true VLAN device.
next prev parent reply other threads:[~2004-10-20 6:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OF1AA93F13.5E509602-ONC1256F2E.00506148-C1256F2E.00551602@de.ibm.com>
2004-10-15 23:27 ` FWD: setting skb->dev to vlan device in vlan_hwaccel_rx is wrong Ben Greear
2004-10-20 6:36 ` David S. Miller [this message]
2004-10-20 8:08 ` Frank Pavlic
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=20041019233618.6fdcb01d.davem@redhat.com \
--to=davem@redhat.com \
--cc=greearb@candelatech.com \
--cc=netdev@oss.sgi.com \
--cc=pavlic@de.ibm.com \
--cc=vlan@candelatech.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).