From: Gopal Yadav <gopunop@gmail.com>
To: Florian Westphal <fw@strlen.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [nftables] TODO: Replace yy_switch_to_buffer by yypop_buffer_state and yypush_buffer_state
Date: Wed, 9 Sep 2020 21:40:22 +0530 [thread overview]
Message-ID: <CAAUOv8jy2ryt8hS3BsmgNZAyU5Kc1qFw2L1UoHrB3L_qE98AFQ@mail.gmail.com> (raw)
In-Reply-To: <20200909122354.GP7319@breakpoint.cc>
On Wed, Sep 9, 2020 at 5:53 PM Florian Westphal <fw@strlen.de> wrote:
>
> Gopal Yadav <gopunop@gmail.com> wrote:
> > Are there any beginner friendly issues to solve or any other
> > starting point?
>
> This one for example:
> https://bugzilla.netfilter.org/show_bug.cgi?id=1305
>
> Its "just" a documentation issue. You could work from comment 4
> and improve the nft documentation to clarify 'accept' behaviour.
>
> For many other bugs it would help if we had testcases that demonstrated
> this problem in the nftables.git repo.
>
> So, if you can translate a BZ ticker to e.g. a new test case in
> tests/shell that show problem still exists in current nftables.git then
> you could submit that test case as a patch, even if the problem is not
> yet resolved.
>
> Readily available test reproducers help a lot.
Thanks for the reply. Pablo suggested to work on
https://bugzilla.netfilter.org/show_bug.cgi?id=1388
but I think his mail was not sent to the mailing list.
I am currently trying to solve that one. Will get back to look at 1305
after that.
next prev parent reply other threads:[~2020-09-09 16:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-08 13:05 [nftables] TODO: Replace yy_switch_to_buffer by yypop_buffer_state and yypush_buffer_state Gopal Yadav
2020-09-09 12:23 ` Florian Westphal
2020-09-09 16:10 ` Gopal Yadav [this message]
2020-09-11 18:19 ` Gopal Yadav
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=CAAUOv8jy2ryt8hS3BsmgNZAyU5Kc1qFw2L1UoHrB3L_qE98AFQ@mail.gmail.com \
--to=gopunop@gmail.com \
--cc=fw@strlen.de \
--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).