Skip to content

Commit 72e6258

Browse files
nam-ngnam-ng
committed
Merge remote-tracking branch 'upstream/main'
2 parents 1fe691b + ac2c383 commit 72e6258

File tree

510 files changed

+9998
-7884
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

510 files changed

+9998
-7884
lines changed

‎.github/CODEOWNERS‎

Lines changed: 39 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,39 @@
1+
# Each line is a file pattern followed by one or more owners.
2+
3+
# These owners will be the default owners for everything in
4+
# the repo. Unless a later match takes precedence,
5+
# @global-owner1 and @global-owner2 will be requested for
6+
# review when someone opens a pull request.
7+
* @FreeRTOS/pr-bar-raiser
8+
9+
# Order is important; the last matching pattern takes the most
10+
# precedence. When someone opens a pull request that only
11+
# modifies JS files, only @js-owner and not the global
12+
# owner(s) will be requested for a review.
13+
# *.c FreeRTOS/pr-bar-raiser
14+
15+
# You can also use email addresses if you prefer. They'll be
16+
# used to look up users just like we do for commit author
17+
# emails.
18+
# *.go [email protected]
19+
20+
# In this example, @doctocat owns any files in the build/logs
21+
# directory at the root of the repository and any of its
22+
# subdirectories.
23+
# /build/logs/ @doctocat
24+
25+
# The `docs/*` pattern will match files like
26+
# `docs/getting-started.md` but not further nested files like
27+
# `docs/build-app/troubleshooting.md`.
28+
# docs/* [email protected]
29+
30+
# In this example, @octocat owns any file in an apps directory
31+
# anywhere in your repository.
32+
# apps/ @octocat
33+
34+
# In this example, @doctocat owns any file in the `/docs`
35+
# directory in the root of your repository and any of its
36+
# subdirectories.
37+
# /docs/ @doctocat
38+
39+

CONTRIBUTING.md renamed to .github/CONTRIBUTING.md

Lines changed: 70 additions & 70 deletions
Original file line numberDiff line numberDiff line change
@@ -1,70 +1,70 @@
1-
# Contribution guidelines
2-
3-
Thank you for your interest in contributing to our project. Whether it's a bug report, new feature, code, or
4-
documentation, we welcome our community to be involved in this project.
5-
6-
Please read through this document before submitting any issues or pull requests to ensure we are able to help you and all members of the community as effectively as possible.
7-
8-
## Code of conduct
9-
This project has adopted the [Amazon Open Source Code of Conduct](https://aws.github.io/code-of-conduct).
10-
For more information see the [Code of Conduct FAQ](https://aws.github.io/code-of-conduct-faq) or contact
11-
[email protected] with any additional questions or comments.
12-
13-
14-
## Security issue notifications
15-
If you discover a potential security issue in this project we ask that you notify AWS/Amazon Security via our [vulnerability reporting page](https://aws.amazon.com/security/vulnerability-reporting/). Please do **not** create a public github issue.
16-
17-
18-
## Submitting a bugs/feature request
19-
Have a bug to report or feature to request? Follow these steps:
20-
1. Search on the [FreeRTOS Community Support Forums](https://forums.freertos.org/) and [GitHub issue tracker](https://github.com/FreeRTOS/FreeRTOS/issues?utf8=%E2%9C%93&q=is%3Aissue) to be sure this hasn't been already reported or discussed.
21-
2. If your search turns up empty, create a new topic in the [forums](https://forums.freertos.org/) and work with the community to help clarify issues or refine the idea. Include as many of the details listed below.
22-
3. Once the community has had time to discuss and digest, we welcome you to create an [issue](https://github.com/FreeRTOS/FreeRTOS/issues) to report bugs or suggest features.
23-
24-
When creating a new topic on the forums or filing an issue, please include as many relevant details as possible. Examples include:
25-
26-
* A clear description of the situation — what you observe, what you expect, and your view on how the two differ.
27-
* A reproducible test case or sequence of steps.
28-
* The version of our code being used.
29-
* Any modifications you've made relevant to the bug.
30-
* Details of your environment or deployment. Highlight anything unusual.
31-
32-
33-
## Contributing via pull request
34-
Contributions via pull requests are much appreciated. Before sending us a pull request, please ensure that:
35-
36-
1. You are working against the latest source on the *master* branch.
37-
2. You check existing open, and recently merged, pull requests to make sure someone else hasn't addressed the problem already.
38-
3. You open an issue to discuss any significant work - we would hate for your time to be wasted.
39-
40-
To send us a pull request, please:
41-
42-
1. Fork the repository.
43-
2. Modify the source; focus on the specific change you are contributing. If you also reformat all the code, it will be hard for us to focus on your change.
44-
3. Follow the [coding style guide](https://www.FreeRTOS.org/FreeRTOS-Coding-Standard-and-Style-Guide.html).
45-
4. Commit to your fork using clear commit messages.
46-
5. Send us a pull request, answering any default questions in the pull request interface.
47-
NOTE: Please make sure the default option (Allow edits from maintainers) is left checked.
48-
6. Pay attention to any automated CI failures reported in the pull request, and stay involved in the conversation.
49-
50-
GitHub provides additional document on [forking a repository](https://help.github.com/articles/fork-a-repo/) and
51-
[creating a pull request](https://help.github.com/articles/creating-a-pull-request/).
52-
53-
## Coding style
54-
* Please ensure that your code complies to the [FreeRTOS coding style guidelines](https://www.FreeRTOS.org/FreeRTOS-Coding-Standard-and-Style-Guide.html).
55-
56-
57-
## Getting your pull request merged
58-
All pull requests must be approved by our review team before it can be merged in. We appreciate your patience while pull requests are reviewed. The time it takes to review will depend on complexity and consideration of wider implications.
59-
60-
61-
## Finding contributions to work on
62-
Looking at the existing issues is a great way to find something to contribute on. As our projects, by default, use the default GitHub issue labels (enhancement/bug/duplicate/help wanted/invalid/question/wontfix), tackling open 'help wanted' issues is a great place to start.
63-
64-
65-
## Licensing
66-
The FreeRTOS kernel is released under the MIT open source license, the text of which can be found [here](https://github.com/FreeRTOS/FreeRTOS/blob/master/FreeRTOS/License/license.txt)
67-
68-
Additional license files can be found in the folders containing any supplementary libraries licensed by their respective copyright owners where applicable.
69-
70-
We may ask you to sign a [Contributor License Agreement (CLA)](https://en.wikipedia.org/wiki/Contributor_License_Agreement) for larger changes.
1+
# Contribution guidelines
2+
3+
Thank you for your interest in contributing to our project. Whether it's a bug report, new feature, code, or
4+
documentation, we welcome our community to be involved in this project.
5+
6+
Please read through this document before submitting any issues or pull requests to ensure we are able to help you and all members of the community as effectively as possible.
7+
8+
## Code of conduct
9+
This project has adopted the [Amazon Open Source Code of Conduct](https://aws.github.io/code-of-conduct).
10+
For more information see the [Code of Conduct FAQ](https://aws.github.io/code-of-conduct-faq) or contact
11+
[email protected] with any additional questions or comments.
12+
13+
14+
## Security issue notifications
15+
If you discover a potential security issue in this project we ask that you notify AWS/Amazon Security via our [vulnerability reporting page](https://aws.amazon.com/security/vulnerability-reporting/). Please do **not** create a public github issue.
16+
17+
18+
## Submitting a bugs/feature request
19+
Have a bug to report or feature to request? Follow these steps:
20+
1. Search on the [FreeRTOS Community Support Forums](https://forums.freertos.org/) and [GitHub issue tracker](https://github.com/FreeRTOS/FreeRTOS/issues?utf8=%E2%9C%93&q=is%3Aissue) to be sure this hasn't been already reported or discussed.
21+
2. If your search turns up empty, create a new topic in the [forums](https://forums.freertos.org/) and work with the community to help clarify issues or refine the idea. Include as many of the details listed below.
22+
3. Once the community has had time to discuss and digest, we welcome you to create an [issue](https://github.com/FreeRTOS/FreeRTOS/issues) to report bugs or suggest features.
23+
24+
When creating a new topic on the forums or filing an issue, please include as many relevant details as possible. Examples include:
25+
26+
* A clear description of the situation — what you observe, what you expect, and your view on how the two differ.
27+
* A reproducible test case or sequence of steps.
28+
* The version of our code being used.
29+
* Any modifications you've made relevant to the bug.
30+
* Details of your environment or deployment. Highlight anything unusual.
31+
32+
33+
## Contributing via pull request
34+
Contributions via pull requests are much appreciated. Before sending us a pull request, please ensure that:
35+
36+
1. You are working against the latest source on the *main* branch.
37+
2. You check existing open, and recently merged, pull requests to make sure someone else hasn't addressed the problem already.
38+
3. You open an issue to discuss any significant work - we would hate for your time to be wasted.
39+
40+
To send us a pull request, please:
41+
42+
1. Fork the repository.
43+
2. Modify the source; focus on the specific change you are contributing. If you also reformat all the code, it will be hard for us to focus on your change.
44+
3. Follow the [coding style guide](https://www.FreeRTOS.org/FreeRTOS-Coding-Standard-and-Style-Guide.html).
45+
4. Commit to your fork using clear commit messages.
46+
5. Send us a pull request, answering any default questions in the pull request interface.
47+
NOTE: Please make sure the default option (Allow edits from maintainers) is left checked.
48+
6. Pay attention to any automated CI failures reported in the pull request, and stay involved in the conversation.
49+
50+
GitHub provides additional document on [forking a repository](https://help.github.com/articles/fork-a-repo/) and
51+
[creating a pull request](https://help.github.com/articles/creating-a-pull-request/).
52+
53+
## Coding style
54+
* Please ensure that your code complies to the [FreeRTOS coding style guidelines](https://www.FreeRTOS.org/FreeRTOS-Coding-Standard-and-Style-Guide.html).
55+
56+
57+
## Getting your pull request merged
58+
All pull requests must be approved by our review team before it can be merged in. We appreciate your patience while pull requests are reviewed. The time it takes to review will depend on complexity and consideration of wider implications.
59+
60+
61+
## Finding contributions to work on
62+
Looking at the existing issues is a great way to find something to contribute on. As our projects, by default, use the default GitHub issue labels (enhancement/bug/duplicate/help wanted/invalid/question/wontfix), tackling open 'help wanted' issues is a great place to start.
63+
64+
65+
## Licensing
66+
The FreeRTOS kernel is released under the MIT open source license, the text of which can be found [here](https://github.com/FreeRTOS/FreeRTOS/blob/main/FreeRTOS/License/license.txt)
67+
68+
Additional license files can be found in the folders containing any supplementary libraries licensed by their respective copyright owners where applicable.
69+
70+
We may ask you to sign a [Contributor License Agreement (CLA)](https://en.wikipedia.org/wiki/Contributor_License_Agreement) for larger changes.

‎.github/ISSUE_TEMPLATE/bug-report.md‎

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,8 @@
11
---
22
name: Bug report
3-
about: Create a report to help us improve our code.
3+
about: Create a report to help us improve FreeRTOS. This should only be used for confirmed
4+
bugs. If you suspect something it is best to first discuss it on the FreeRTOS community
5+
support forums linked below.
46
title: "[BUG]"
57
labels: bug
68
assignees: ''

‎.github/ISSUE_TEMPLATE/config.yml‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
blank_issues_enabled: false
2+
contact_links:
3+
- name: FreeRTOS Community Support Forum
4+
url: https://forums.freertos.org/
5+
about: Please ask and answer questions about FreeRTOS here.
6+

‎.github/ISSUE_TEMPLATE/feature_request.md‎

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
---
2+
name: Feature request
3+
about: Suggest a new feature for this project
4+
title: "[Feature Request] <replace with your title>"
5+
labels: enhancement
6+
assignees: ''
7+
8+
---
9+
10+
**Is your feature request related to a problem? Please describe.**
11+
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
12+
13+
**Describe the solution you'd like**
14+
A clear and concise description of what you want to happen.
15+
16+
**Describe alternatives you've considered**
17+
A clear and concise description of any alternative solutions or features you've considered.
18+
19+
**Additional context**
20+
Add any other context or screenshots about the feature request here.

SECURITY.md renamed to .github/SECURITY.md

File renamed without changes.

‎.github/actions/url_verifier.sh‎

Lines changed: 63 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,63 @@
1+
#!/bin/bash -
2+
3+
PROJECT=$1
4+
echo "Verifying url links of: ${PROJECT}"
5+
if [ ! -d "$PROJECT" ]
6+
then
7+
echo "Directory passed does not exist"
8+
exit 2
9+
fi
10+
11+
USER_AGENT="Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.146 Safari/537.36"
12+
SCRIPT_RET=0
13+
14+
set -o nounset # Treat unset variables as an error
15+
16+
declare -A dict
17+
18+
function test {
19+
while IFS= read -r LINE; do
20+
FILE=$(echo $LINE | cut -f 1 -d ':')
21+
URL=$(echo $LINE | grep -IoE '\b(https?|ftp|file)://[-A-Za-z0-9+&@#/%?=~_|!:,.;]*[-A-Za-z0-9+&@#/%=~_|]')
22+
23+
# remove trailing / if it exists curl diferenciate between links with
24+
# and without / at the end
25+
# URL=`echo "$URL" | sed 's,/$,,'`
26+
dict+=(["$URL"]="$FILE ")
27+
done < <(grep -e 'https\?://' ${PROJECT} -RIa --exclude='*.exe' --exclude-dir=.git | tr '*' ' ')
28+
29+
for UNIQ_URL in ${!dict[@]} # loop urls
30+
do
31+
CURL_RES=$(curl -si --user-agent "$(USER_AGENT)" ${UNIQ_URL} 2>/dev/null| head -n 1 | cut -f 2 -d ' ')
32+
RES=$?
33+
34+
if [ "${CURL_RES}" == '' -o "${CURL_RES}" != '200' ]
35+
then
36+
echo "URL is: ${UNIQ_URL}"
37+
echo "File names: ${dict[$UNIQ_URL]}"
38+
if [ "${CURL_RES}" == '' ] # curl returned an error
39+
then
40+
CURL_RES=$RES
41+
SCRIPT_RET=1
42+
echo ERROR: Result is: "${CURL_RES}"
43+
elif [ "${CURL_RES}" == '403' ]
44+
then
45+
SCRIPT_RET=1
46+
echo ERROR: Result is: "${CURL_RES}"
47+
else
48+
echo WARNING: Result is: "${CURL_RES}"
49+
fi
50+
echo "================================="
51+
fi
52+
done
53+
54+
if [ "${SCRIPT_RET}" -eq 0 ]
55+
then
56+
exit 0
57+
else
58+
exit 1
59+
fi
60+
}
61+
62+
test
63+

lexicon.txt renamed to .github/lexicon.txt

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1529,6 +1529,7 @@ prvinitialisenewstreambuffer
15291529
prvinitialisenewtimer
15301530
prvinsertblockintofreelist
15311531
prvlockqueue
1532+
prvnotifyqueuesetcontainer
15321533
prvportmalloc
15331534
prvportresetpic
15341535
prvprocesssimulatedinterrupts
@@ -1617,6 +1618,7 @@ pvowner
16171618
pvparameter
16181619
pvparameters
16191620
pvportmalloc
1621+
pvportmallocstack
16201622
pvportrealloc
16211623
pvreg
16221624
pvrxdata
@@ -1686,6 +1688,7 @@ pxprevious
16861688
pxpreviouswaketime
16871689
pxqueue
16881690
pxqueuebuffer
1691+
pxqueuesetcontainer
16891692
pxramstack
16901693
pxreadycoroutinelists
16911694
pxreadytaskslists
@@ -1705,6 +1708,7 @@ pxstreambuffercreatestatic
17051708
pxtagvalue
17061709
pxtask
17071710
pxtaskbuffer
1711+
pxtaskcode
17081712
pxtaskdefinition
17091713
pxtaskstatus
17101714
pxtaskstatusarray
@@ -2976,6 +2980,7 @@ xtaskcreate
29762980
xtaskcreaterestricted
29772981
xtaskcreaterestrictedstatic
29782982
xtaskcreatestatic
2983+
xtaskdelayuntil
29792984
xtaskdetails
29802985
xtaskendscheduler
29812986
xtaskgetapplicationtasktag
@@ -3016,6 +3021,7 @@ xtaskswaitingforbits
30163021
xtaskswaitingtermination
30173022
xtaskswaitingtoreceive
30183023
xtaskswaitingtosend
3024+
xtasktodelete
30193025
xtasktonotify
30203026
xtasktoquery
30213027
xtasktoresume
@@ -3076,6 +3082,7 @@ xvalueofinsertion
30763082
xvtorconst
30773083
xwaitforallbits
30783084
xwantedsize
3085+
xwasdelayed
30793086
xwritevalue
30803087
xxr
30813088
xyieldpending

0 commit comments

Comments
 (0)