From: christian.babeux@efficios.com (Christian Babeux)
Subject: [lttng-dev] [PATCH lttng-ust] Fix: Fix self-assign warning on struct ustfork_clone_info init
Date: Tue, 23 Oct 2012 15:37:20 -0400 [thread overview]
Message-ID: <1351021040-18587-1-git-send-email-christian.babeux@efficios.com> (raw)
Use the proper field designator syntax (C99) to initialize the
ustfork_clone_info struct.
Signed-off-by: Christian Babeux <christian.babeux at efficios.com>
---
liblttng-ust-fork/ustfork.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
mode change 100644 => 100755 liblttng-ust-fork/ustfork.c
diff --git a/liblttng-ust-fork/ustfork.c b/liblttng-ust-fork/ustfork.c
old mode 100644
new mode 100755
index 13f77cf..34f674c
--- a/liblttng-ust-fork/ustfork.c
+++ b/liblttng-ust-fork/ustfork.c
@@ -139,7 +139,7 @@ int clone(int (*fn)(void *), void *child_stack, int flags, void *arg, ...)
tls, ctid);
} else {
/* Creating a real process, we need to intervene. */
- struct ustfork_clone_info info = { fn = fn, arg = arg };
+ struct ustfork_clone_info info = { .fn = fn, .arg = arg };
ust_before_fork(&info.sigset);
retval = plibc_func(clone_fn, child_stack, flags, &info,
--
1.7.12.2
next reply other threads:[~2012-10-23 19:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-23 19:37 Christian Babeux [this message]
2012-10-23 19:59 ` Mathieu Desnoyers
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=1351021040-18587-1-git-send-email-christian.babeux@efficios.com \
--to=christian.babeux@efficios.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