github-starred/cs249r_book
2
0
Fork 0
mirror of https://github.com/harvard-edge/cs249r_book.git synced 2026-05-08 02:28:25 -05:00
Code Issues 85 Packages Projects Releases 24 Wiki Activity

[PR #54] [MERGED] Updates to Embedded Systems Chapter #3191

New Issue
Closed
opened 2026-04-16 01:41:31 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-16 01:41:31 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/harvard-edge/cs249r_book/pull/54
Author: @Ekhao
Created: 11/10/2023
Status: ✅ Merged
Merged: 11/10/2023
Merged by: @profvjreddi

Base: main ← Head: embedded-systems-updates

📝 Commits (5)

  • b1ec0c3 corrected arm sales paragraph
  • 95ebd37 updated real time scheduler subsection
  • 531795e Merge branch 'harvard-edge:main' into embedded-systems-updates
  • 4f2f38c Merge branch 'embedded-systems-updates' of github.com:Ekhao/cs249r_book into embedded-systems-updates
  • f718e50 missing word

📊 Changes

1 file changed (+5 additions, -3 deletions)

View changed files

📝 embedded_sys.qmd (+5 -3)

📄 Description

This pull request makes relatively small changes to the embedded systems chapter. Namely it fixes a paragraph on ARM sales figures that could be misunderstood and rewrites the real time scheduling subsection to discuss how static schedules can be used to guarantee response times instead of discussing priority scheduling which also exist in non-real time scheduling.

The checklist below seems to be meant for full chapter contributions, but I have filled it out the best I could!

  1. Content

    • The chapter content is complete and covers the topic in detail.
    • All technical terms are well-defined and explained.
    • Any code snippets or algorithms are well-documented and tested.
    • The chapter follows a logical flow and structure.

  2. References & Citations

    • All references are correctly listed at the end of the chapter.
    • In-text citations are used appropriately and match the references.
    • All figures, tables, and images have proper sources and are cited correctly.

  3. Quarto Website Rendering

    • The chapter has been locally built and tested using Quarto.
    • All images, figures, and tables render properly without any glitches.
    • All images have a source or they are properly linked to external sites.
    • Any interactive elements or widgets work as intended.
    • The chapter's formatting is consistent with the rest of the book.

  4. Grammar & Style

    • The chapter has been proofread for grammar and spelling errors.
    • The writing style is consistent with the rest of the book.
    • Any jargon is clearly explained or avoided where possible.

  5. Collaboration

    • All group members have reviewed and approved the chapter.
    • Any feedback from previous reviews or discussions has been addressed.

  6. Miscellaneous

    • All external links (if any) are working and lead to the intended destinations.
    • If datasets or external resources are used, they are properly credited and linked.
    • Any necessary permissions for reused content have been obtained.

  7. Final Steps

    • The chapter is pushed to the correct branch on the repository.
    • The Pull Request is made with a clear title and description.
    • The Pull Request includes any necessary labels or tags.
    • The Pull Request mentions any stakeholders or reviewers who should take a look.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/harvard-edge/cs249r_book/pull/54 **Author:** [@Ekhao](https://github.com/Ekhao) **Created:** 11/10/2023 **Status:** ✅ Merged **Merged:** 11/10/2023 **Merged by:** [@profvjreddi](https://github.com/profvjreddi) **Base:** `main` ← **Head:** `embedded-systems-updates` --- ### 📝 Commits (5) - [`b1ec0c3`](https://github.com/harvard-edge/cs249r_book/commit/b1ec0c38b839dea150325e59c645a0bf58ed76df) corrected arm sales paragraph - [`95ebd37`](https://github.com/harvard-edge/cs249r_book/commit/95ebd37e224a00f8f3833bb37d0abb50a5fff25b) updated real time scheduler subsection - [`531795e`](https://github.com/harvard-edge/cs249r_book/commit/531795e5583d49d1f502f711451e5de96635878d) Merge branch 'harvard-edge:main' into embedded-systems-updates - [`4f2f38c`](https://github.com/harvard-edge/cs249r_book/commit/4f2f38c178fcc7ba3a44ef8a943eadd73915d4f0) Merge branch 'embedded-systems-updates' of github.com:Ekhao/cs249r_book into embedded-systems-updates - [`f718e50`](https://github.com/harvard-edge/cs249r_book/commit/f718e50ef137b9f27f868b0d5e1142a7fe0726d7) missing word ### 📊 Changes **1 file changed** (+5 additions, -3 deletions) <details> <summary>View changed files</summary> 📝 `embedded_sys.qmd` (+5 -3) </details> ### 📄 Description This pull request makes relatively small changes to the embedded systems chapter. Namely it fixes a paragraph on ARM sales figures that could be misunderstood and rewrites the real time scheduling subsection to discuss how static schedules can be used to guarantee response times instead of discussing priority scheduling which also exist in non-real time scheduling. The checklist below seems to be meant for full chapter contributions, but I have filled it out the best I could! 1. **Content** - [x] The chapter content is complete and covers the topic in detail. - [x] All technical terms are well-defined and explained. - [x] Any code snippets or algorithms are well-documented and tested. - [x] The chapter follows a logical flow and structure. 2. **References & Citations** - [x] All references are correctly listed at the end of the chapter. - [x] In-text citations are used appropriately and match the references. - [x] All figures, tables, and images have proper sources and are cited correctly. 3. **Quarto Website Rendering** - [x] The chapter has been locally built and tested using Quarto. - [x] All images, figures, and tables render properly without any glitches. - [x] All images have a source or they are properly linked to external sites. - [x] Any interactive elements or widgets work as intended. - [x] The chapter's formatting is consistent with the rest of the book. 4. **Grammar & Style** - [x] The chapter has been proofread for grammar and spelling errors. - [x] The writing style is consistent with the rest of the book. - [x] Any jargon is clearly explained or avoided where possible. 5. **Collaboration** - [ ] All group members have reviewed and approved the chapter. - [ ] Any feedback from previous reviews or discussions has been addressed. 6. **Miscellaneous** - [x] All external links (if any) are working and lead to the intended destinations. - [x] If datasets or external resources are used, they are properly credited and linked. - [x] Any necessary permissions for reused content have been obtained. 7. **Final Steps** - [x] The chapter is pushed to the correct branch on the repository. - [x] The Pull Request is made with a clear title and description. - [ ] The Pull Request includes any necessary labels or tags. - [ ] The Pull Request mentions any stakeholders or reviewers who should take a look. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-16 01:41:31 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area: book
area: collabs
area: kits
area: socratiq
area: tinytorch
area: tools
area: website
bug
dependencies
format: epub
format: pdf
link-health
link-rot
priority-high
pull-request
Mirrored from GitHub Pull Request
 staffml
type: bug
type: citation
type: code
type: errata
type: improvement
type: new
type: question
vault-sli
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/cs249r_book#3191
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?