public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Marcos Paulo de Souza <marcos@mpdesouza.com>
Cc: Marcos Paulo de Souza <mpdesouza@suse.com>,
	dsterba@suse.com, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 2/3] progs: Include btrfs-find-root and btrfs-select-super in testsuite
Date: Mon, 2 Mar 2020 08:02:32 +0800	[thread overview]
Message-ID: <c0521ff0-2adb-0ef5-3dbe-e4f698188ec0@gmx.com> (raw)
In-Reply-To: <20200301033344.808-3-marcos@mpdesouza.com>


[-- Attachment #1.1: Type: text/plain, Size: 1397 bytes --]



On 2020/3/1 上午11:33, Marcos Paulo de Souza wrote:
> From: Marcos Paulo de Souza <mpdesouza@suse.com>
> 
> Since these two binaries are not shipped into userspace, and they are
> used by the testsuite, they need to be include in the final tar.
> 
> Signed-off-by: Marcos Paulo de Souza <mpdesouza@suse.com>
Reviewed-by: Qu Wenruo <wqu@suse.com>

Just a small nitpick, the prefix for the patch should be "btrfs-progs: "
not "progs: ".

Thanks,
Qu
> ---
>  Makefile              | 2 +-
>  tests/testsuite-files | 2 ++
>  2 files changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/Makefile b/Makefile
> index b00eafe4..0cd7f0c1 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -424,7 +424,7 @@ test-inst: all
>  
>  test: test-fsck test-mkfs test-misc test-cli test-convert test-fuzz
>  
> -testsuite: btrfs-corrupt-block fssum
> +testsuite: btrfs-corrupt-block btrfs-find-root btrfs-select-super fssum
>  	@echo "Export tests as a package"
>  	$(Q)cd tests && ./export-testsuite.sh
>  
> diff --git a/tests/testsuite-files b/tests/testsuite-files
> index 09df6298..507d35fb 100644
> --- a/tests/testsuite-files
> +++ b/tests/testsuite-files
> @@ -3,6 +3,8 @@ G Documentation/
>  F testsuite-id
>  F ../fssum
>  F ../btrfs-corrupt-block
> +F ../btrfs-find-root
> +F ../btrfs-select-super
>  F common
>  F common.convert
>  F common.local
> 


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2020-03-02  0:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-01  3:33 [PATCH 0/3] progs: fix testsuite Marcos Paulo de Souza
2020-03-01  3:33 ` [PATCH 1/3] progs: Remove manpages of not packaged binaries Marcos Paulo de Souza
2020-03-01  8:26   ` Qu Wenruo
2020-03-01 14:28     ` Marcos Paulo de Souza
2020-03-02 20:02       ` David Sterba
2020-03-01  3:33 ` [PATCH 2/3] progs: Include btrfs-find-root and btrfs-select-super in testsuite Marcos Paulo de Souza
2020-03-02  0:02   ` Qu Wenruo [this message]
2020-03-01  3:33 ` [PATCH 3/3] progs: tests: misc: btrfs-{find-root,select-super} are internal commands Marcos Paulo de Souza
2020-03-02  0:03   ` Qu Wenruo

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=c0521ff0-2adb-0ef5-3dbe-e4f698188ec0@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=dsterba@suse.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=marcos@mpdesouza.com \
    --cc=mpdesouza@suse.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