From: Harsha Sharma <harshasharmaiitr@gmail.com>
To: netfilter-devel@vger.kernel.org
Cc: outreachy-kernel@googlegroups.com, harshasharmaiitr@gmail.com
Subject: nftables: Add support for reserved header and addrs for routing header type 0
Date: Wed, 04 Oct 2017 12:37:26 +0530 [thread overview]
Message-ID: <1507100846.10633.17.camel@harryPotter> (raw)
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].
Can anyone please guide me on how to declare macros in parser_bison.c?
Thanks for your time.
Regards,
Harsha Sharma
next reply other threads:[~2017-10-04 7:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-04 7:07 Harsha Sharma [this message]
2017-10-04 11:10 ` nftables: Add support for reserved header and addrs for routing header type 0 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=1507100846.10633.17.camel@harryPotter \
--to=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).