-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clarify and unify naming of thread-related constants (stacksize and priority) #2881
Conversation
#define KERNEL_CONF_STACKSIZE_PRINTF_FLOAT (8192) | ||
#define THREAD_STACKSIZE_DEFAULT (8192) | ||
#define THREAD_STACKSIZE_IDLE (8192) | ||
#define THREAD_EXTRA_STACKSIZE_PRINTF (8192) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Indentation is off.
You're planning to squash? Otherwise the commit messages are missing a proper prefix. |
Yep, planning to squash. Or would you say the commits should stay this way? Then I'd rename |
* @def THREAD_PRIORITY_IDLE | ||
* @brief Priority of the idle thread | ||
*/ | ||
#define THREAD_PRIORITY_IDLE THREAD_PRIORITY_MIN |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would prefer to put parenthesis around this
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Even though it just maps to THREAD_PRIORITY_MIN which is in parentheses?
ACK when comment above is addressed |
ACK |
looks good please squash, then lets see what travis says |
adeb101
to
eed76f2
Compare
Please rebase |
@authmillenon Will do. Travis was unhappy about smth and I didn't manage to fix that yet, but I'll give my best to get it merged asap. |
Any news? |
eed76f2
to
abf650f
Compare
Since I've touched a lot of files in this PR, I also have to deal with a lot of doxygen warnings that I have no clue how to fix. How do we handle this? |
Travis should only complain if the PR introduces doxygen warnings. |
Does it not complain about all warnings in files that have been changed in a PR? That was my impression so far. |
See https://github.com/RIOT-OS/RIOT/blob/master/dist/tools/doccheck/check.sh#L12:
Hence, only created and copied files should create errors, the rest should output only warnings. |
5c20fec
to
1183747
Compare
1183747
to
e5bc5a4
Compare
@OlegHahm The last Travis build passed but there was a minor merge conflict :( Can I merge this as soon as Travis comes back with a green light? It's ACKed otherwise, right? |
Yes, you can. |
f7cb1c7
to
cf10a66
Compare
a0f4b7a
to
f0bf928
Compare
As discussed in RIOT-OS#2725, this commit renames a number of stacksize constants to better convey their intended usage. In addition, constants for thread priority are given a `THREAD_` prefix. Changes are: * KERNEL_CONF_STACKSIZE_PRINTF renamed to THREAD_EXTRA_STACKSIZE_PRINTF * KERNEL_CONF_STACKSIZE_DEFAULT renamed to THREAD_STACKSIZE_DEFAULT * KERNEL_CONF_STACKSIZE_IDLE renamed to THREAD_STACKSIZE_IDLE * KERNEL_CONF_STACKSIZE_MAIN renamed to THREAD_STACKSIZE_MAIN * Move thread stacksizes from kernel.h to thread.h, since the prefix changed * PRIORITY_MIN renamed to THREAD_PRIORITY_MIN * PRIORITY_IDLE renamed to THREAD_PRIORITY_IDLE * PRIORITY_MAIN renamed to THREAD_PRIORITY_MAIN * Move thread priorities from kernel.h to thread.h since the prefix has changed * MINIMUM_STACK_SIZE renamed to THREAD_STACKSIZE_MINIMUM for consistency
|
f0bf928
to
426170b
Compare
Build passed over at my fork's Travis. Is it okay if I merge? |
Works for me. |
Then brace for impact 💥 |
Clarify and unify naming of thread-related constants (stacksize and priority)
Sry, this is too late now and maybe it´s a dump question. Why are the old auto-init apps introduced again? And why in this PR?
What exactly needs to be updated there? |
If they should not be there, then I probably messed up one of the many rebases :( |
Ah ok, yes they should not be there. The PR that changed the auto-init process is #2901. Maybe this was merged before your last rebase or so. But this doesn´t break anything, so the files could just be deleted by any follow-up or so. Just asked because this could affect the driver implementation for kw2xrf. |
Changes as discussed in #2725
KERNEL_CONF
prefix in favor ofTHREAD
.KERNEL_CONF_STACKSIZE_DEFAULT
becomesTHREAD_STACKSIZE_DEFAULT
.KERNEL_CONF
prefix in favor ofEXTRA
.KERNEL_CONF_STACKSIZE_PRINTF
becomesTHREAD_EXTRA_STACKSIZE_PRINTF
.In addition:
PRIORITY_...
are now prefixed withTHREAD_
MINIMUM_STACK_SIZE
adapted to the naming scheme of the other stacksizes, thus becomingTHREAD_STACKSIZE_MINIMUM