From: Daniel Borkmann <daniel@iogearbox.net>
To: Florian Westphal <fw@strlen.de>, netdev@vger.kernel.org
Subject: Re: [PATCH -next] net: sched: remove TC_MUNGED bits
Date: Fri, 01 May 2015 14:55:58 +0200 [thread overview]
Message-ID: <554377DE.6070106@iogearbox.net> (raw)
In-Reply-To: <1430388720-5112-1-git-send-email-fw@strlen.de>
On 04/30/2015 12:12 PM, Florian Westphal wrote:
> Not used.
>
> pedit sets TC_MUNGED when packet content was altered, but all the core
> does is unset MUNGED again and then set OK2MUNGE.
>
> And the latter isn't tested anywhere. So lets remove both
> TC_MUNGED and TC_OK2MUNGE.
>
> Signed-off-by: Florian Westphal <fw@strlen.de>
Also looks good, thanks Florian!
Acked-by: Daniel Borkmann <daniel@iogearbox.net>
next prev parent reply other threads:[~2015-05-01 12:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-30 10:12 [PATCH -next] net: sched: remove TC_MUNGED bits Florian Westphal
2015-04-30 21:16 ` Alexei Starovoitov
2015-05-01 0:43 ` Jamal Hadi Salim
2015-05-01 9:46 ` Florian Westphal
2015-05-01 12:15 ` Jamal Hadi Salim
2015-05-01 12:55 ` Daniel Borkmann [this message]
2015-05-03 2:25 ` 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=554377DE.6070106@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=fw@strlen.de \
--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).