From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: davem@davemloft.net, Tom Herbert <tom@herbertland.com>,
edumazet@google.com, netdev@vger.kernel.org,
dan.carpenter@oracle.com
Subject: Re: [PATCH net-next 2/2] flow_dissector: add support for dst, hop-by-hop and routing ext hdrs
Date: Fri, 12 Jun 2015 19:15:35 -0700 [thread overview]
Message-ID: <20150613021534.GA9942@Alexeis-MacBook-Pro.local> (raw)
In-Reply-To: <1434161476.27504.105.camel@edumazet-glaptop2.roam.corp.google.com>
On Fri, Jun 12, 2015 at 07:11:16PM -0700, Eric Dumazet wrote:
> On Fri, 2015-06-12 at 18:50 -0700, Alexei Starovoitov wrote:
>
> >
> > sure, that's better.
> > If you're going to submit it officialy, please add my Tested-by.
> > My server is happy now :)
>
> Sure , will do.
>
> I tried adding __must_check to __skb_header_pointer() but apparently had
> to use W=1 to get a warning :
that is great idea still. At least buildbot can pick it up.
next prev parent reply other threads:[~2015-06-13 2:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-12 16:01 [PATCH net-next 0/2] flow_dissector: Fix MPLS parsing and add ext hdr support Tom Herbert
2015-06-12 16:01 ` [PATCH net-next 1/2] flow_dissector: Fix MPLS entropy label handling in flow dissector Tom Herbert
2015-06-12 16:01 ` [PATCH net-next 2/2] flow_dissector: add support for dst, hop-by-hop and routing ext hdrs Tom Herbert
2015-06-13 1:27 ` Alexei Starovoitov
2015-06-13 1:37 ` Eric Dumazet
2015-06-13 1:50 ` Alexei Starovoitov
2015-06-13 2:11 ` Eric Dumazet
2015-06-13 2:15 ` Alexei Starovoitov [this message]
2015-06-13 2:31 ` [PATCH net-next] flow_dissector: fix ipv6 " Eric Dumazet
2015-06-13 2:40 ` Tom Herbert
2015-06-13 4:59 ` David Miller
2015-06-12 21:24 ` [PATCH net-next 0/2] flow_dissector: Fix MPLS parsing and add ext hdr support 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=20150613021534.GA9942@Alexeis-MacBook-Pro.local \
--to=alexei.starovoitov@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=tom@herbertland.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).