Skip to content
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.

Sign up for GitHub

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

Jump to bottom

doc/mainpage: don't claim to be a microkernel #20246

Merged
merged 1 commit into from
Jan 12, 2024
Merged

doc/mainpage: don't claim to be a microkernel #20246

merged 1 commit into from
Jan 12, 2024

Conversation

benpicco
Copy link
Contributor

@benpicco benpicco commented Jan 11, 2024 •
edited
Loading

Contribution description

Don't call RIOT a microkernel, that just sets the wrong expectations.
We only have threads, but no separation between them or any notion of kernel/userspace.
By that notion Linux would also be a microkernel.

Testing procedure

Issues/PRs references

@github-actions github-actions bot added the Area: doc Area: Documentation label Jan 11, 2024
@benpicco benpicco added CI: skip compile test If set, CI server will run only non-compile jobs, but no compile jobs or their dependent jobs CI: ready for build If set, CI server will compile all applications for all available boards for the labeled PR labels Jan 11, 2024
@maribu maribu added the Process: needs >1 ACK Integration Process: This PR requires more than one ACK label Jan 11, 2024
@github-actions github-actions bot added the Process: missing approvals Integration Process: PR needs more ACKS (handled by action) label Jan 11, 2024
@benpicco
doc/mainpage: don't claim to be a microkernel
ca97f8a 
We are clearly not and this just sets wrong expectations.
@github-actions github-actions bot added the Area: core Area: RIOT kernel. Handle PRs marked with this with care! label Jan 11, 2024
@riot-ci
Copy link

riot-ci commented Jan 11, 2024

Murdock results

✔️ PASSED

ca97f8a doc/mainpage: don't claim to be a microkernel

Success Failures Total Runtime
1 0 1 01m:01s

Artifacts

@chrysn
Copy link
Member

chrysn commented Jan 11, 2024

For context, the earlierst mention of the term on that page's history was in 2013 by @OlegHahm in 4f45305, the oldest mention in-tree was in 784ef52 in 2012 also by Oleg.

@mguetschow mguetschow mentioned this pull request Jan 12, 2024
Merged
@benpicco benpicco removed the Process: missing approvals Integration Process: PR needs more ACKS (handled by action) label Jan 12, 2024
@benpicco benpicco added this pull request to the merge queue Jan 12, 2024
Merged via the queue into RIOT-OS:master with commit 31da90e Jan 12, 2024
26 of 27 checks passed
@benpicco benpicco deleted the microkernel branch January 12, 2024 08:53
@MrKevinWeiss MrKevinWeiss added this to the Release 2024.01 milestone Feb 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@mguetschow mguetschow mguetschow approved these changes

@maribu maribu maribu approved these changes

@aabadie aabadie Awaiting requested review from aabadie aabadie is a code owner

@jia200x jia200x Awaiting requested review from jia200x jia200x is a code owner

@chrysn chrysn Awaiting requested review from chrysn

@OlegHahm OlegHahm Awaiting requested review from OlegHahm

@emmanuelsearch emmanuelsearch Awaiting requested review from emmanuelsearch

@kaspar030 kaspar030 Awaiting requested review from kaspar030 kaspar030 is a code owner

Assignees
No one assigned
Labels
Area: core Area: RIOT kernel. Handle PRs marked with this with care! Area: doc Area: Documentation CI: ready for build If set, CI server will compile all applications for all available boards for the labeled PR CI: skip compile test If set, CI server will run only non-compile jobs, but no compile jobs or their dependent jobs Process: needs >1 ACK Integration Process: This PR requires more than one ACK
Projects
None yet
Milestone
Release 2024.01
Development

Successfully merging this pull request may close these issues.
6 participants
@benpicco @riot-ci @chrysn @maribu @mguetschow @MrKevinWeiss