opensbi.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Ivan Orlov <ivan.orlov0322@gmail.com>
To: opensbi@lists.infradead.org
Subject: [PATCH 3/3] docs: writing tests: update cleaning instructions
Date: Mon,  1 Apr 2024 22:34:38 +0100	[thread overview]
Message-ID: <20240401213438.590209-4-ivan.orlov0322@gmail.com> (raw)
In-Reply-To: <20240401213438.590209-1-ivan.orlov0322@gmail.com>

After the changes introduced by the previous patches are applied, there
is no need of the manual removal of the `build/` directory every time
new test is added. Running `make clean` should be enough to regenerate
the carray-related files.

Update the documentation correspondingly.

Signed-off-by: Ivan Orlov <ivan.orlov0322@gmail.com>
---
 docs/writing_tests.md | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/docs/writing_tests.md b/docs/writing_tests.md
index 0fd15d6..cee4c4d 100644
--- a/docs/writing_tests.md
+++ b/docs/writing_tests.md
@@ -57,9 +57,7 @@ carray-sbi_unit_tests-$(CONFIG_SBIUNIT) += string_test_suite
 libsbi-objs-$(CONFIG_SBIUNIT) += tests/sbi_string_test.o
 ```
 
-If you compiled OpenSBI with CONFIG_SBIUNIT enabled before, you may need to
-manually remove the build folder in order to regenerate the carray files:
-`rm -rf build/`.
+Now, run `make clean` in order to regenerate the carray-related files.
 
 Recompile OpenSBI with the CONFIG_SBIUNIT option enabled and run it in QEMU.
 You will see something like this:
-- 
2.34.1



  parent reply	other threads:[~2024-04-01 21:34 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-01 21:34 [PATCH 0/3] CArray improvements Ivan Orlov
2024-04-01 21:34 ` [PATCH 1/3] Makefile: clean auto-generated *.c files properly Ivan Orlov
2024-04-22 15:19   ` Andrew Jones
2024-04-23 14:58     ` Ivan Orlov
2024-04-23 15:15       ` Ben Dooks
2024-04-23 15:18       ` Andrew Jones
2024-04-23 15:20       ` Ben Dooks
2024-04-23 15:24         ` Ben Dooks
2024-04-23 15:26         ` Ben Dooks
2024-04-23 15:41           ` Ivan Orlov
2024-04-26 16:25             ` Ben Dooks
2024-04-29  8:52               ` Andrew Jones
2024-04-29 12:16                 ` Ben Dooks
2024-04-29 13:11                 ` Ben Dooks
2024-04-01 21:34 ` [PATCH 2/3] scripts/carray.sh: Add comment to generated files Ivan Orlov
2024-04-22 15:21   ` Andrew Jones
2024-04-23 15:25   ` Ben Dooks
2024-04-01 21:34 ` Ivan Orlov [this message]
2024-04-22 15:22   ` [PATCH 3/3] docs: writing tests: update cleaning instructions Andrew Jones
2024-05-07  6:06 ` [PATCH 0/3] CArray improvements Anup Patel
2024-05-10 15:56   ` Ivan Orlov

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=20240401213438.590209-4-ivan.orlov0322@gmail.com \
    --to=ivan.orlov0322@gmail.com \
    --cc=opensbi@lists.infradead.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).