All of lore.kernel.org
 help / color / mirror / Atom feed
From: chrubis@suse.cz
To: Alexey Kodanev <alexey.kodanev@oracle.com>
Cc: vasily.isaenko@oracle.com, ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH] doc: test-writing-guidelines
Date: Thu, 27 Mar 2014 14:52:39 +0100	[thread overview]
Message-ID: <20140327135239.GD4234@rei> (raw)
In-Reply-To: <1395926898-11327-1-git-send-email-alexey.kodanev@oracle.com>

Hi!
> Add thread-safety paragraph
> Add example of how to use TST_DECLARE_ONCE_FN

Pushed with minor changes:

diff --git a/doc/test-writing-guidelines.txt b/doc/test-writing-guidelines.txt
index a7250b7..9c3ea2a 100644
--- a/doc/test-writing-guidelines.txt
+++ b/doc/test-writing-guidelines.txt
@@ -675,12 +675,12 @@ bellow:
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 It is safe to use library 'tst_' functions in multi-threaded tests.
-Synchronization mechanism enabled only if the test is linked with pthread
+Synchronization mechanism is enabled only if the test is linked with pthread
 library, otherwise no-op stubs (defined in libc) are used.
 
-Also, LTP has a help "TST_DECLARE_ONCE_FN" macro to declare a function which
-must be run only once (e.g. init or cleanup function), but might be called
-by multiple threads in the same time. See example below:
+Also, LTP has a helper "TST_DECLARE_ONCE_FN" macro to declare a function which
+must be run only once (e.g. init or cleanup function), but might be called by
+multiple threads at the same time. See example below:


And also updated the online version in GitHub wiki. Thanks.

-- 
Cyril Hrubis
chrubis@suse.cz

------------------------------------------------------------------------------
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  reply	other threads:[~2014-03-27 13:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-27 13:28 [LTP] [PATCH] doc: test-writing-guidelines Alexey Kodanev
2014-03-27 13:52 ` chrubis [this message]
2014-05-08  5:42 Xiaoguang Wang
2014-05-13 13:39 ` chrubis
2014-05-14  5:16 Xiaoguang Wang
2014-05-14 11:46 ` chrubis
2014-06-18  6:31 Xiaoguang Wang
2014-06-18 11:37 ` chrubis

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=20140327135239.GD4234@rei \
    --to=chrubis@suse.cz \
    --cc=alexey.kodanev@oracle.com \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=vasily.isaenko@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.