From: Guillaume Nault <gnault@redhat.com>
To: David Ahern <dsahern@gmail.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
Stephen Hemminger <stephen@networkplumber.org>,
netdev@vger.kernel.org
Subject: Re: [PATCH iproute2] tc: flower: fix json output with mpls lse
Date: Mon, 11 Jan 2021 11:57:44 +0100 [thread overview]
Message-ID: <20210111105744.GA13412@linux.home> (raw)
In-Reply-To: <31cfb1dc-1e93-e3ed-12f4-f8c44adfd535@gmail.com>
On Thu, Jan 07, 2021 at 10:39:03AM -0700, David Ahern wrote:
> On 1/7/21 10:13 AM, Jakub Kicinski wrote:
> > On Thu, 7 Jan 2021 17:48:56 +0100 Guillaume Nault wrote:
> >> On Fri, Dec 18, 2020 at 11:25:32PM +0100, Guillaume Nault wrote:
> >>> The json output of the TCA_FLOWER_KEY_MPLS_OPTS attribute was invalid.
> >>>
> >>> Example:
> >>>
> >>> $ tc filter add dev eth0 ingress protocol mpls_uc flower mpls \
> >>> lse depth 1 label 100 \
> >>> lse depth 2 label 200
> >>>
> >>> $ tc -json filter show dev eth0 ingress
> >>> ...{"eth_type":"8847",
> >>> " mpls":[" lse":["depth":1,"label":100],
> >>> " lse":["depth":2,"label":200]]}...
> >>
> >> Is there any problem with this patch?
> >> It's archived in patchwork, but still in state "new". Therefore I guess
> >> it was dropped before being considered for review.
> >
> > Erm, that's weird. I think Alexei mentioned that auto-archiving is
> > turned on in the new netdevbpf patchwork instance. My guess is it got
> > auto archived :S
> >
> > Here is the list of all patches that are Archived as New:
> >
> > https://patchwork.kernel.org/project/netdevbpf/list/?state=1&archive=true
> >
> > Should any of these have been reviewed?
> >
>
>
> Interesting. I thought some patches had magically disappeared - and some
> of those are in that list.
Okay, but, in the end, should I repost this patch?
next prev parent reply other threads:[~2021-01-11 10:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-18 22:25 [PATCH iproute2] tc: flower: fix json output with mpls lse Guillaume Nault
2021-01-07 16:48 ` Guillaume Nault
2021-01-07 17:13 ` Jakub Kicinski
2021-01-07 17:39 ` David Ahern
2021-01-11 10:57 ` Guillaume Nault [this message]
2021-01-11 15:30 ` David Ahern
2021-01-11 15:44 ` Guillaume Nault
2021-01-11 16:02 ` David Ahern
2021-01-11 16:06 ` Guillaume Nault
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=20210111105744.GA13412@linux.home \
--to=gnault@redhat.com \
--cc=dsahern@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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 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.