From: Thomas Monjalon <thomas@monjalon.net>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: Cody Doucette <doucette@bu.edu>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
dev@dpdk.org, Gaetan Rivet <gaetan.rivet@6wind.com>,
Olivier Matz <olivier.matz@6wind.com>,
"Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>,
Michel Machado <michel@digirati.com.br>,
"Fu, Qiaobin" <qiaobinf@bu.edu>
Subject: Re: [PATCH v3] ip_frag: extend rte_ipv6_frag_get_ipv6_fragment_header()
Date: Thu, 01 Nov 2018 15:07:50 +0100 [thread overview]
Message-ID: <9397707.3THrMnljP8@xps> (raw)
In-Reply-To: <20181101135356.GA27151@hmswarspite.think-freely.org>
01/11/2018 14:53, Neil Horman:
> On Wed, Oct 31, 2018 at 04:08:18PM +0100, Thomas Monjalon wrote:
> > 31/10/2018 16:03, Neil Horman:
> > > On Wed, Oct 31, 2018 at 10:20:46AM -0400, Cody Doucette wrote:
> > > > Thanks for the suggestion. It looks like
> > > > 49bcce138374458d1edd1c50d8e5726959108ef4 is already in my tree. I tried
> > > > applying and checking again anyway and it seems that the error is still
> > > > present.
> > > >
> > > Thats not a commit in the upstream tree, I've no idea what patch you are referring to
> >
> > Yes it is in the tree, in 18.11-rc1.
> >
> Got it now, thanks.
>
> So this actually looks to be a new bug, and I'm not sure how it got in there.
> The awk match to close the in_map section isn't triggering on this patch set,
> which is very odd, as Its been working. The match is ^(map) which should be ok
> (allbeit perl regex syntax), which I thought awk supported. That said, it
> certainly doesn't seem to be matching now.
All these regex things are painful sometimes :)
> I've got a patch posted to you which replaces this with a traditional character
> class match [^map], and thats working with this patch set.
OK, I'll check it, thanks.
prev parent reply other threads:[~2018-11-01 14:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-27 13:52 [PATCH v3] ip_frag: extend rte_ipv6_frag_get_ipv6_fragment_header() Cody Doucette
2018-08-20 19:31 ` Cody Doucette
2018-10-28 10:21 ` Thomas Monjalon
2018-10-28 20:54 ` Cody Doucette
2018-10-28 21:19 ` Thomas Monjalon
2018-10-30 9:46 ` Ananyev, Konstantin
2018-10-30 14:36 ` Thomas Monjalon
2018-10-30 18:09 ` Cody Doucette
2018-10-30 23:12 ` Thomas Monjalon
2018-10-31 9:27 ` Neil Horman
2018-10-31 14:20 ` Cody Doucette
2018-10-31 15:03 ` Neil Horman
2018-10-31 15:08 ` Thomas Monjalon
2018-11-01 13:53 ` Neil Horman
2018-11-01 14:07 ` Thomas Monjalon [this message]
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=9397707.3THrMnljP8@xps \
--to=thomas@monjalon.net \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=doucette@bu.edu \
--cc=gaetan.rivet@6wind.com \
--cc=konstantin.ananyev@intel.com \
--cc=michel@digirati.com.br \
--cc=nhorman@tuxdriver.com \
--cc=olivier.matz@6wind.com \
--cc=qiaobinf@bu.edu \
/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.