Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
NuttX RTOS
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Container Registry
Model registry
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
f4grx
NuttX RTOS
Commits
61819c0e
Commit
61819c0e
authored
9 years ago
by
Gregory Nutt
Browse files
Options
Downloads
Patches
Plain Diff
Fix a typo in last commit that was not noticed until CONFIG_SIG_EVTHREAD was enabled
parent
da5115e3
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
sched/timer/timer_create.c
+5
-5
5 additions, 5 deletions
sched/timer/timer_create.c
with
5 additions
and
5 deletions
sched/timer/timer_create.c
+
5
−
5
View file @
61819c0e
...
...
@@ -218,13 +218,13 @@ int timer_create(clockid_t clockid, FAR struct sigevent *evp, FAR timer_t *timer
* timer ID."
*/
ret
->
pt_event
.
sigev_notify
=
SIGEV_SIGNAL
;
ret
->
pt_event
.
sigev_signo
=
SIGALRM
;
ret
->
pt_event
.
sigev_value
.
sival_ptr
=
ret
;
ret
->
pt_event
.
sigev_notify
=
SIGEV_SIGNAL
;
ret
->
pt_event
.
sigev_signo
=
SIGALRM
;
ret
->
pt_event
.
sigev_value
.
sival_ptr
=
ret
;
#ifdef CONFIG_SIG_EVTHREAD
ret
->
pt_event
.
sigev_
value
.
sigev_
notify_function
=
NULL
;
ret
->
pt_event
.
sigev_
value
.
sigev_
notify_attributes
=
NULL
;
ret
->
pt_event
.
sigev_notify_function
=
NULL
;
ret
->
pt_event
.
sigev_notify_attributes
=
NULL
;
#endif
}
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment