netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Varsha Rao <rvarsha016@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nft 00/16] tests: files: Remove test files.
Date: Mon, 6 Nov 2017 16:04:34 +0100	[thread overview]
Message-ID: <20171106150434.GA20966@salvia> (raw)
In-Reply-To: <cover.1509305217.git.rvarsha016@gmail.com>

Hi Varsha,

On Mon, Oct 30, 2017 at 02:09:24AM +0530, Varsha Rao wrote:
> This patch removes tests from tests/files and add tests to 
> tests/shell which are not present in it.
> 
> Varsha Rao (16):
>   tests: files: Remove tests for ipv4
>   tests: files: Remove tests for ipv6
>   tests: shell: Add test for log statement.

I think we have a test for this under tests/py.

>   tests: files: Remove log statement tests.
>   tests: shell: Add test for log flags.
>   tests: shell: Add tests for payload expression.

Same thing for these to..

>   tests: files: Remove payload expression tests.
>   tests: files: Remove test for syntactical errors.
>   tests: shell: Add test for ct expression.

Same thing.

>   tests: files: Remove test for ct expression.
>   tests: files: Remove prefix file.
>   tests: files: Test for meta expressions.

Same thing.

>   tests: files: Remove test for meta expression.
>   tests: shell: Add tests for concat expression.

Same thing... so it looks like you can send a patch to remove them all
in one go.

Thanks a lot for reviewing what we had under tests/files/

>   tests: files: Remove tests for concat expression.
>   tests: shell: Add test case for map expression.

BTW, I have applied 16/16.

      parent reply	other threads:[~2017-11-06 15:04 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-29 20:39 [PATCH nft 00/16] tests: files: Remove test files Varsha Rao
2017-10-29 20:49 ` [PATCH nft 01/16] tests: files: Remove tests for ipv4 Varsha Rao
2017-10-29 20:49   ` [PATCH nft 02/16] tests: files: Remove tests for ipv6 Varsha Rao
2017-10-29 20:49   ` [PATCH nft 03/16] tests: shell: Add test for log statement Varsha Rao
2017-10-29 20:49   ` [PATCH nft 04/16] tests: files: Remove log statement tests Varsha Rao
2017-10-29 20:49   ` [PATCH nft 05/16] tests: shell: Add test for log flags Varsha Rao
2017-10-29 20:49   ` [PATCH nft 06/16] tests: shell: Add tests for payload expression Varsha Rao
2017-10-29 20:49   ` [PATCH nft 07/16] tests: files: Remove payload expression tests Varsha Rao
2017-10-29 20:49   ` [PATCH nft 08/16] tests: files: Remove test for syntactical errors Varsha Rao
2017-10-29 20:49   ` [PATCH nft 09/16] tests: shell: Add test for ct expression Varsha Rao
2017-10-29 20:49   ` [PATCH nft 10/16] tests: files: Remove " Varsha Rao
2017-10-29 20:49   ` [PATCH nft 11/16] tests: files: Remove prefix file Varsha Rao
2017-10-29 20:49   ` [PATCH nft 12/16] tests: files: Test for meta expressions Varsha Rao
2017-10-29 20:49   ` [PATCH nft 13/16] tests: files: Remove test for meta expression Varsha Rao
2017-10-29 20:49   ` [PATCH nft 14/16] tests: shell: Add tests for concat expression Varsha Rao
2017-10-29 20:49   ` [PATCH nft 15/16] tests: files: Remove " Varsha Rao
2017-10-29 20:49   ` [PATCH nft 16/16] tests: shell: Add test case for map expression Varsha Rao
2017-11-06 15:04 ` 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=20171106150434.GA20966@salvia \
    --to=pablo@netfilter.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=rvarsha016@gmail.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).