From: Florian Westphal <fw@strlen.de>
To: Karuna Grewal <karunagrewal98@gmail.com>
Cc: Florian Westphal <fw@strlen.de>, netfilter-devel@vger.kernel.org
Subject: Re: [nftables] tests/py: Add Test for `meta time`
Date: Tue, 19 Mar 2019 08:50:38 +0100 [thread overview]
Message-ID: <20190319075038.3t2jvc3vcje55h6k@breakpoint.cc> (raw)
In-Reply-To: <CAHRz_yZe8j_83vTjYXbBHME69Qd=X0XfoR-5A81KoqKqWKP53g@mail.gmail.com>
Karuna Grewal <karunagrewal98@gmail.com> wrote:
> Thanks. I checked that in the userspace the enum nft_meta_keys has
> additional values as compared to the linux 5.0.2 's nft_meta_keys but
> this isn't the case with the nf-next.
> I'll run the tests again with the nf-next kernel tree.
> Also, does this mean that I should stick to the nf-next kernel tree
> instead of the latest kernel release itself?
nf-next lags behind at the moment, it will catch up soon.
So, meanwhile you can use nf or even linus tree until nf-next is
back in sync.
next prev parent reply other threads:[~2019-03-19 7:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-18 9:47 [nftables] tests/py: Add Test for `meta time` Karuna Grewal
[not found] ` <CAHRz_yZMsP2RQPu=8pTigq8SrYz9xYSef3S_d4ORAMkkYDEv4Q@mail.gmail.com>
[not found] ` <20190318105545.qz5oddbjah4qc4fa@breakpoint.cc>
[not found] ` <CAHRz_yYk_Yq5+Tp1J1jT2rVT0pHWjH37-F8Rdi1XCLWj79J6rg@mail.gmail.com>
[not found] ` <20190318220923.5v64yccan6shhpnq@breakpoint.cc>
2019-03-19 7:04 ` Karuna Grewal
2019-03-19 7:17 ` Florian Westphal
2019-03-19 7:27 ` Karuna Grewal
2019-03-19 7:50 ` Florian Westphal [this message]
2019-04-08 22:35 ` Pablo Neira Ayuso
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=20190319075038.3t2jvc3vcje55h6k@breakpoint.cc \
--to=fw@strlen.de \
--cc=karunagrewal98@gmail.com \
--cc=netfilter-devel@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).