From: Junchang Wang <junchangwang@gmail.com>
To: paulmck@linux.ibm.com
Cc: perfbook@vger.kernel.org, Junchang Wang <junchangwang@gmail.com>
Subject: [PATCH 1/3] route_hazptr: Add dependency to hazptr
Date: Sat, 24 Nov 2018 17:34:52 +0800 [thread overview]
Message-ID: <1543052094-8306-2-git-send-email-junchangwang@gmail.com> (raw)
In-Reply-To: <1543052094-8306-1-git-send-email-junchangwang@gmail.com>
Target route_hazptr depends on hazptr.c and hazptr.h. So add this dependency to Makefile.
Signed-off-by: Junchang Wang <junchangwang@gmail.com>
---
CodeSamples/defer/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/CodeSamples/defer/Makefile b/CodeSamples/defer/Makefile
index 5a08c1f..270c151 100644
--- a/CodeSamples/defer/Makefile
+++ b/CodeSamples/defer/Makefile
@@ -123,7 +123,7 @@ rcu_sig: rcu_sig.c rcu_sig.h ../api.h rcutorture.h
rcu_ts: rcu_ts.c rcu_ts.h ../api.h rcutorture.h
cc $(GCC_ARGS) -o rcu_ts -DTEST rcu_ts.c -lpthread
-route_hazptr: route_hazptr.c ../api.h ../lib/random.h ../lib/random.c routetorture.h
+route_hazptr: route_hazptr.c hazptr.c hazptr.h ../api.h ../lib/random.h ../lib/random.c routetorture.h
cc $(GCC_ARGS) -o route_hazptr route_hazptr.c hazptr.c ../lib/random.c -lpthread
route_rcu: route_rcu.c ../api.h ../lib/random.h ../lib/random.c routetorture.h
--
2.7.4
next prev parent reply other threads:[~2018-11-24 9:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-24 9:34 [PATCH 0/3] Patches for Section Deferred Processing Junchang Wang
2018-11-24 9:34 ` Junchang Wang [this message]
2018-11-24 9:34 ` [PATCH 2/3] route_hazptr: Fix a memory leak bug Junchang Wang
2018-11-24 9:34 ` [PATCH 3/3] defer: Fix a typo Junchang Wang
2018-11-24 16:47 ` [PATCH 0/3] Patches for Section Deferred Processing Paul E. McKenney
2018-11-25 2:18 ` Junchang Wang
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=1543052094-8306-2-git-send-email-junchangwang@gmail.com \
--to=junchangwang@gmail.com \
--cc=paulmck@linux.ibm.com \
--cc=perfbook@vger.kernel.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 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.