From: David Miller <davem@davemloft.net>
To: rick.jones2@hp.com
Cc: eric.dumazet@gmail.com, raj@tardy.usa.hp.com,
netdev@vger.kernel.org, sshah@solarflare.com,
linux-net-drivers@solarflare.com
Subject: Re: [PATCH net-next] sfc: Convert the normal transmit complete path to dev_consume_skb_any()
Date: Tue, 09 Sep 2014 16:46:24 -0700 (PDT) [thread overview]
Message-ID: <20140909.164624.687652552683224035.davem@davemloft.net> (raw)
In-Reply-To: <540F8F78.9020502@hp.com>
From: Rick Jones <rick.jones2@hp.com>
Date: Tue, 09 Sep 2014 16:38:32 -0700
> But perhaps someone from SolarFlare can say why that was a const to
> begin with.
Probably to trap skb->x modifications after the SKB has been placed
in these entries, except for these explicit spots where the casts
are applied.
next prev parent reply other threads:[~2014-09-09 23:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-09 21:43 [PATCH net-next] sfc: Convert the normal transmit complete path to dev_consume_skb_any() Rick Jones
2014-09-09 23:18 ` Eric Dumazet
2014-09-09 23:38 ` Rick Jones
2014-09-09 23:46 ` David Miller [this message]
2014-09-10 0:25 ` Eric Dumazet
2014-09-10 0:34 ` 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=20140909.164624.687652552683224035.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=linux-net-drivers@solarflare.com \
--cc=netdev@vger.kernel.org \
--cc=raj@tardy.usa.hp.com \
--cc=rick.jones2@hp.com \
--cc=sshah@solarflare.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).