From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Harsha Sharma <harshasharmaiitr@gmail.com>
Cc: netfilter-devel@vger.kernel.org, outreachy-kernel@googlegroups.com
Subject: Re: nftables: Add support for reserved header and addrs for routing header type 0
Date: Wed, 4 Oct 2017 13:10:25 +0200 [thread overview]
Message-ID: <20171004111025.GB2575@salvia> (raw)
In-Reply-To: <1507100846.10633.17.camel@harryPotter>
On Wed, Oct 04, 2017 at 12:37:26PM +0530, Harsha Sharma wrote:
> Hello,
> I'm working on task for adding support for reserved header and addrs for
> routing header type 0 in nftables. The code already uses macros like
> [RT0HDR_RESERVED], [RT0HDR_ADDR_1] in extensions/exthdr.c but they are
> not declared in parser_bison.c like other macros [RTHDR_TYPE] and
> [RTHDR_NEXTHDR].
They are indeed declared, please take the time to familiarize with
'git grep' to search for token on the git repository.
Thanks.
prev parent reply other threads:[~2017-10-04 11:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-04 7:07 nftables: Add support for reserved header and addrs for routing header type 0 Harsha Sharma
2017-10-04 11:10 ` Pablo Neira Ayuso [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=20171004111025.GB2575@salvia \
--to=pablo@netfilter.org \
--cc=harshasharmaiitr@gmail.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=outreachy-kernel@googlegroups.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).