dev  

Messages by Thread

• [DISCUSS] Breaking change: remove BOARDIOC_SPINLOCK (apache/nuttx#21696) Marco C.
  • Re: [DISCUSS] Breaking change: remove BOARDIOC_SPINLOCK (apache/nuttx#21696) Alin Jerpelea
  • Re: [DISCUSS] Breaking change: remove BOARDIOC_SPINLOCK (apache/nuttx#21696) Nathan Hartman
• [PR] tests: use assert True in the test resources [nuttx-ntfc] raiden00pl (via GitHub) via dev
  • Re: [PR] tests: use assert True in the test resources [nuttx-ntfc] xiaoxiang781216 (via GitHub) via dev
• [PR] device: add the console over a NuttX netdev console [nuttx-ntfc] raiden00pl (via GitHub) via dev
• [VOTE] Release NuttX 13.1.1 jerpelea.apache.org via dev
  • Re: [VOTE] Release NuttX 13.1.1 Alan C. Assis
  • Re: [VOTE] Release NuttX 13.1.1 michallenc.apache.org via dev
  • Re: [VOTE] Release NuttX 13.1.1 kr . git
• Any stm32h7 available reviewers? Peter Barada
  • Re: Any stm32h7 available reviewers? Alan C. Assis
  • Re: Any stm32h7 available reviewers? Nathan Hartman
• [DISCUSS] AGENTS.md: make AI-assisted contributions follow our rules Marco C.
  • Re: [DISCUSS] AGENTS.md: make AI-assisted contributions follow our rules Alin Jerpelea
  • Re: [DISCUSS] AGENTS.md: make AI-assisted contributions follow our rules Sarthak Pandey
  • Re: [DISCUSS] AGENTS.md: make AI-assisted contributions follow our rules Alan C. Assis
  • Re: [DISCUSS] AGENTS.md: make AI-assisted contributions follow our rules chao an
  • Re: [DISCUSS] AGENTS.md: make AI-assisted contributions follow our rules Marco C.
  • Re: [DISCUSS] AGENTS.md: make AI-assisted contributions follow our rules Marco C.
  • Re: [DISCUSS] AGENTS.md: make AI-assisted contributions follow our rules Matteo Golin
  • Re: [DISCUSS] AGENTS.md: make AI-assisted contributions follow our rules kr . git
  • Re: [DISCUSS] AGENTS.md: make AI-assisted contributions follow our rules Tomek CEDRO
  • Re: [DISCUSS] AGENTS.md: make AI-assisted contributions follow our rules Marco C.
  • Re: [DISCUSS] AGENTS.md: make AI-assisted contributions follow our rules Tomek CEDRO
• [DISCUSS] POSIX job control: real process groups, sessions and controlling terminals Marco C.
  • Re: [DISCUSS] POSIX job control: real process groups, sessions and controlling terminals kr . git
• Nuttian: a NuttX-based distribution with dpkg/apt (proof of concept) Marco C.
• [VOTE] Integration model for a Zephyr-based Bluetooth host in NuttX �ɿ� via dev
  • Re: [VOTE] Integration model for a Zephyr-based Bluetooth host in NuttX Alan C. Assis
  • Re: [VOTE] Integration model for a Zephyr-based Bluetooth host in NuttX Alin Jerpelea
  • Re: [VOTE] Integration model for a Zephyr-based Bluetooth host in NuttX chao an
  • Re: [VOTE] Integration model for a Zephyr-based Bluetooth host in NuttX Xiang Xiao
  • Re: [VOTE] Integration model for a Zephyr-based Bluetooth host in NuttX Xiang Xiao
  • Re: [VOTE] Integration model for a Zephyr-based Bluetooth host in NuttX Alan C. Assis
  • Re: [VOTE] Integration model for a Zephyr-based Bluetooth host in NuttX Nathan Hartman
  • Re: [VOTE] Integration model for a Zephyr-based Bluetooth host in NuttX Tomek CEDRO
  • [RESULT][VOTE] Integration model for a Zephyr-based Bluetooth host in NuttX �ɿ� via dev
• Formal Request for NFS Infrastructure Verification, Data Preservation and Recovery Assistance – Historical NuttX/PX4 Development Work Siddhartha Sharma
  • Re: Formal Request for NFS Infrastructure Verification, Data Preservation and Recovery Assistance – Historical NuttX/PX4 Development Work Alan C. Assis
  • Re: Formal Request for NFS Infrastructure Verification, Data Preservation and Recovery Assistance – Historical NuttX/PX4 Development Work Marco C.
  • Re: Formal Request for NFS Infrastructure Verification, Data Preservation and Recovery Assistance – Historical NuttX/PX4 Development Work Siddhartha Sharma
  • Re: Formal Request for NFS Infrastructure Verification, Data Preservation and Recovery Assistance – Historical NuttX/PX4 Development Work Marco C.
  • Re: Formal Request for NFS Infrastructure Verification, Data Preservation and Recovery Assistance – Historical NuttX/PX4 Development Work Siddhartha Sharma
  • Re: Formal Request for NFS Infrastructure Verification, Data Preservation and Recovery Assistance – Historical NuttX/PX4 Development Work Siddhartha Sharma
  • Re: Formal Request for NFS Infrastructure Verification, Data Preservation and Recovery Assistance – Historical NuttX/PX4 Development Work Siddhartha Sharma
  • Re: Formal Request for NFS Infrastructure Verification, Data Preservation and Recovery Assistance – Historical NuttX/PX4 Development Work Alan C. Assis
  • Re: Formal Request for NFS Infrastructure Verification, Data Preservation and Recovery Assistance – Historical NuttX/PX4 Development Work Nathan Hartman
• Proposal: Shadow-mode evaluation of NuttX CI architecture selection Arnav Sharma
  • Re: Proposal: Shadow-mode evaluation of NuttX CI architecture selection Alan C. Assis
• {DISCUSS} NuttX Release plan Alin Jerpelea
  • Re: {DISCUSS} NuttX Release plan Xiang Xiao
  • Re: {DISCUSS} NuttX Release plan Michal Lenc
  • Re: {DISCUSS} NuttX Release plan Alan C. Assis
  • Re: {DISCUSS} NuttX Release plan Tomek CEDRO
  • Re: {DISCUSS} NuttX Release plan Michal Lenc
  • Re: {DISCUSS} NuttX Release plan Tomek CEDRO
  • Re: {DISCUSS} NuttX Release plan Alin Jerpelea
  • Re: {DISCUSS} NuttX Release plan Alin Jerpelea
• Should we cherry-pick many patches from dev to release branch after it is created? Xiang Xiao
  • Re: Should we cherry-pick many patches from dev to release branch after it is created? Alin Jerpelea
  • Re: Should we cherry-pick many patches from dev to release branch after it is created? Alan C. Assis
  • Re: Should we cherry-pick many patches from dev to release branch after it is created? Alin Jerpelea
  • Re: Should we cherry-pick many patches from dev to release branch after it is created? Alan C. Assis
  • Re: Should we cherry-pick many patches from dev to release branch after it is created? Alin Jerpelea
  • Re: Should we cherry-pick many patches from dev to release branch after it is created? Alan C. Assis
  • Re: Should we cherry-pick many patches from dev to release branch after it is created? Alin Jerpelea
  • Re: Should we cherry-pick many patches from dev to release branch after it is created? Xiang Xiao
  • Re: Should we cherry-pick many patches from dev to release branch after it is created? Alin Jerpelea
  • Re: Should we cherry-pick many patches from dev to release branch after it is created? Xiang Xiao
  • Re: Should we cherry-pick many patches from dev to release branch after it is created? Alin Jerpelea
  • Re: Should we cherry-pick many patches from dev to release branch after it is created? Alin Jerpelea
• [RESULT][VOTE] Make CLOCKS_PER_SEC 1000000 (breaking change, PR #20947) Marco C.
• Re: [apache/nuttx] net/bt: Add native Bluetooth host stack (PR #20686) Tomek CEDRO
  • Re: [apache/nuttx] net/bt: Add native Bluetooth host stack (PR #20686) chao an
  • Re: [apache/nuttx] net/bt: Add native Bluetooth host stack (PR #20686) Matteo Golin
  • Re: [apache/nuttx] net/bt: Add native Bluetooth host stack (PR #20686) chao an
• [DISCUSS] Breaking change: the seek function of fopencookie() returns int, as in glibc Marco C.
• my-boardclub.com Tomek CEDRO
• Re: [External Mail]Re: [apache/nuttx] net/bt: Add native Bluetooth host stack (PR #20686) �ɿ� via dev
  • Re: [External Mail]Re: [apache/nuttx] net/bt: Add native Bluetooth host stack (PR #20686) chao an
  • Re: [External Mail]Re: [apache/nuttx] net/bt: Add native Bluetooth host stack (PR #20686) Alan C. Assis
  • Re: [External Mail]Re: [apache/nuttx] net/bt: Add native Bluetooth host stack (PR #20686) chao an
  • Re: [External Mail]Re: [apache/nuttx] net/bt: Add native Bluetooth host stack (PR #20686) Alin Jerpelea
  • Re: [External Mail]Re: [apache/nuttx] net/bt: Add native Bluetooth host stack (PR #20686) chao an
  • Re: [External Mail]Re: [apache/nuttx] net/bt: Add native Bluetooth host stack (PR #20686) Tomek CEDRO
  • Re: [External Mail]Re: [apache/nuttx] net/bt: Add native Bluetooth host stack (PR #20686) chao an
  • Re: [External Mail]Re: [apache/nuttx] net/bt: Add native Bluetooth host stack (PR #20686) chao an
  • Re: [External Mail]Re: [apache/nuttx] net/bt: Add native Bluetooth host stack (PR #20686) Tomek CEDRO
  • Re: [External Mail]Re: [apache/nuttx] net/bt: Add native Bluetooth host stack (PR #20686) chao an
  • Re: [External Mail]Re: [apache/nuttx] net/bt: Add native Bluetooth host stack (PR #20686) kr . git
  • Re: [External Mail]Re: [apache/nuttx] net/bt: Add native Bluetooth host stack (PR #20686) Alan C. Assis
• [DISCUSS] Proposal: integrate a Zephyr-based Bluetooth host (openvela zblue) as a userspace stack in nuttx-apps, kept in sync with upstream Zephyr �ɿ� via dev
  • Re: [External Mail][DISCUSS] Proposal: integrate a Zephyr-based Bluetooth host (openvela zblue) as a userspace stack in nuttx-apps, kept in sync with upstream Zephyr 成凯 via dev
  • Re: [External Mail][DISCUSS] Proposal: integrate a Zephyr-based Bluetooth host (openvela zblue) as a userspace stack in nuttx-apps, kept in sync with upstream Zephyr chao an
  • Re: [DISCUSS] Proposal: integrate a Zephyr-based Bluetooth host (openvela zblue) as a userspace stack in nuttx-apps, kept in sync with upstream Zephyr 成凯 via dev
  • Re: [DISCUSS] Proposal: integrate a Zephyr-based Bluetooth host (openvela zblue) as a userspace stack in nuttx-apps, kept in sync with upstream Zephyr chao an
  • Re: [DISCUSS] Proposal: integrate a Zephyr-based Bluetooth host (openvela zblue) as a userspace stack in nuttx-apps, kept in sync with upstream Zephyr Tomek CEDRO
  • Re: [DISCUSS] Proposal: integrate a Zephyr-based Bluetooth host (openvela zblue) as a userspace stack in nuttx-apps, kept in sync with upstream Zephyr chao an
  • Re: [DISCUSS] Proposal: integrate a Zephyr-based Bluetooth host (openvela zblue) as a userspace stack in nuttx-apps, kept in sync with upstream Zephyr Xiang Xiao
  • Re: [DISCUSS] Proposal: integrate a Zephyr-based Bluetooth host (openvela zblue) as a userspace stack in nuttx-apps, kept in sync with upstream Zephyr chao an
  • Re: [DISCUSS] Proposal: integrate a Zephyr-based Bluetooth host (openvela zblue) as a userspace stack in nuttx-apps, kept in sync with upstream Zephyr Xiang Xiao
  • Re: [DISCUSS] Proposal: integrate a Zephyr-based Bluetooth host (openvela zblue) as a userspace stack in nuttx-apps, kept in sync with upstream Zephyr Alan C. Assis
  • Re: [DISCUSS] Proposal: integrate a Zephyr-based Bluetooth host (openvela zblue) as a userspace stack in nuttx-apps, kept in sync with upstream Zephyr chao an
  • Re: [DISCUSS] Proposal: integrate a Zephyr-based Bluetooth host (openvela zblue) as a userspace stack in nuttx-apps, kept in sync with upstream Zephyr Alan C. Assis
  • Re: [External Mail]Re: [DISCUSS] Proposal: integrate a Zephyr-based Bluetooth host (openvela zblue) as a userspace stack in nuttx-apps, kept in sync with upstream Zephyr 成凯 via dev
• [DISCUSS] Coding standard: EXTERN in header files Marco C.
  • Re: [DISCUSS] Coding standard: EXTERN in header files Nathan Hartman
  • Re: [DISCUSS] Coding standard: EXTERN in header files Marco C.
  • Re: [DISCUSS] Coding standard: EXTERN in header files Nathan Hartman
  • Re: [DISCUSS] Coding standard: EXTERN in header files Alin Jerpelea
  • Re: [DISCUSS] Coding standard: EXTERN in header files Tomek CEDRO
• [RESULT][VOTE] struct pollfd with the POSIX layout (breaking change, PR #20796) Marco C.
• [VOTE] Make CLOCKS_PER_SEC 1000000 (breaking change, PR #20947) Marco C.
  • Re: [VOTE] Make CLOCKS_PER_SEC 1000000 (breaking change, PR #20947) Tomek CEDRO
  • Re: [VOTE] Make CLOCKS_PER_SEC 1000000 (breaking change, PR #20947) Nathan Hartman
  • Re: [VOTE] Make CLOCKS_PER_SEC 1000000 (breaking change, PR #20947) Alin Jerpelea
  • Re: [VOTE] Make CLOCKS_PER_SEC 1000000 (breaking change, PR #20947) Alan C. Assis
• Re: NuttX on my custom 8-bit Microcontroller Tomek CEDRO
• How to see all the CI jobs run for a PR? Peter Barada
• URGENT ACTION NEEDED - Excessive Consumption of GitHub hosted Action Runners Resources Robert Thomson
  • Re: URGENT ACTION NEEDED - Excessive Consumption of GitHub hosted Action Runners Resources Alan C. Assis
  • Re: URGENT ACTION NEEDED - Excessive Consumption of GitHub hosted Action Runners Resources Nathan Hartman
  • Re: URGENT ACTION NEEDED - Excessive Consumption of GitHub hosted Action Runners Resources Alan C. Assis
  • Re: URGENT ACTION NEEDED - Excessive Consumption of GitHub hosted Action Runners Resources Michal Lenc
  • Re: URGENT ACTION NEEDED - Excessive Consumption of GitHub hosted Action Runners Resources Alan C. Assis
  • Re: URGENT ACTION NEEDED - Excessive Consumption of GitHub hosted Action Runners Resources Tomek CEDRO
• [DISCUSS] Breaking change: make CLOCKS_PER_SEC 1000000 Marco C.
  • Re: [DISCUSS] Breaking change: make CLOCKS_PER_SEC 1000000 Xiang Xiao
  • Re: [DISCUSS] Breaking change: make CLOCKS_PER_SEC 1000000 Marco C.
  • Re: [DISCUSS] Breaking change: make CLOCKS_PER_SEC 1000000 Alan C. Assis
  • Re: [DISCUSS] Breaking change: make CLOCKS_PER_SEC 1000000 Gregory Nutt
  • Re: [DISCUSS] Breaking change: make CLOCKS_PER_SEC 1000000 Marco C.
  • Re: [DISCUSS] Breaking change: make CLOCKS_PER_SEC 1000000 kr . git
• [VOTE] struct pollfd with the POSIX layout (breaking change, PR #20796) Marco C.
  • Re: [VOTE] struct pollfd with the POSIX layout (breaking change, PR #20796) Tomek CEDRO
  • Re: [VOTE] struct pollfd with the POSIX layout (breaking change, PR #20796) Alan C. Assis
  • Re: [VOTE] struct pollfd with the POSIX layout (breaking change, PR #20796) Marco C.
  • Re: [VOTE] struct pollfd with the POSIX layout (breaking change, PR #20796) Alan C. Assis
  • Re: [VOTE] struct pollfd with the POSIX layout (breaking change, PR #20796) Nathan Hartman
  • Re: [VOTE] struct pollfd with the POSIX layout (breaking change, PR #20796) Alin Jerpelea
• SDM32H7 SDMMC initialization issue on stm32h7s3l8 Peter Barada
• Is it possible to call upper half code from board code? kr . git
• [DISCUSS] struct pollfd with the POSIX layout (breaking change) Marco C.
  • Re: [DISCUSS] struct pollfd with the POSIX layout (breaking change) Marco C.
  • Re: [DISCUSS] struct pollfd with the POSIX layout (breaking change) Tomek CEDRO
  • Re: [DISCUSS] struct pollfd with the POSIX layout (breaking change) Gregory Nutt
  • Re: [DISCUSS] struct pollfd with the POSIX layout (breaking change) Alin Jerpelea
  • Re: [DISCUSS] struct pollfd with the POSIX layout (breaking change) Tomek CEDRO
  • Re: [DISCUSS] struct pollfd with the POSIX layout (breaking change) Marco C.
  • Re: [DISCUSS] struct pollfd with the POSIX layout (breaking change) Tomek CEDRO
  • Re: [DISCUSS] struct pollfd with the POSIX layout (breaking change) kr . git
• PR #20686 — Introducing a Zephyr-based Bluetooth host stack under net/bt: background, technical motivation, and proposed evolution plan chao an
  • Re: PR #20686 — Introducing a Zephyr-based Bluetooth host stack under net/bt: background, technical motivation, and proposed evolution plan Xiang Xiao
  • Re: PR #20686 — Introducing a Zephyr-based Bluetooth host stack under net/bt: background, technical motivation, and proposed evolution plan chao an
  • Re: PR #20686 — Introducing a Zephyr-based Bluetooth host stack under net/bt: background, technical motivation, and proposed evolution plan Xiang Xiao
  • Re: PR #20686 — Introducing a Zephyr-based Bluetooth host stack under net/bt: background, technical motivation, and proposed evolution plan raiden00pl
  • Re: PR #20686 — Introducing a Zephyr-based Bluetooth host stack under net/bt: background, technical motivation, and proposed evolution plan chao an
  • Re: PR #20686 — Introducing a Zephyr-based Bluetooth host stack under net/bt: background, technical motivation, and proposed evolution plan raiden00pl
  • Re: PR #20686 — Introducing a Zephyr-based Bluetooth host stack under net/bt: background, technical motivation, and proposed evolution plan raiden00pl
  • Re: PR #20686 — Introducing a Zephyr-based Bluetooth host stack under net/bt: background, technical motivation, and proposed evolution plan chao an
  • Re: PR #20686 — Introducing a Zephyr-based Bluetooth host stack under net/bt: background, technical motivation, and proposed evolution plan raiden00pl
  • Re: PR #20686 — Introducing a Zephyr-based Bluetooth host stack under net/bt: background, technical motivation, and proposed evolution plan chao an
  • Re: PR #20686 — Introducing a Zephyr-based Bluetooth host stack under net/bt: background, technical motivation, and proposed evolution plan chao an
  • Re: PR #20686 — Introducing a Zephyr-based Bluetooth host stack under net/bt: background, technical motivation, and proposed evolution plan Xiang Xiao
  • Re: PR #20686 — Introducing a Zephyr-based Bluetooth host stack under net/bt: background, technical motivation, and proposed evolution plan Xiang Xiao
  • Re: PR #20686 — Introducing a Zephyr-based Bluetooth host stack under net/bt: background, technical motivation, and proposed evolution plan raiden00pl
  • Re: PR #20686 — Introducing a Zephyr-based Bluetooth host stack under net/bt: background, technical motivation, and proposed evolution plan chao an
  • Re: PR #20686 — Introducing a Zephyr-based Bluetooth host stack under net/bt: background, technical motivation, and proposed evolution plan chao an
  • Re: PR #20686 — Introducing a Zephyr-based Bluetooth host stack under net/bt: background, technical motivation, and proposed evolution plan Xiang Xiao
  • Re: PR #20686 — Introducing a Zephyr-based Bluetooth host stack under net/bt: background, technical motivation, and proposed evolution plan Alin Jerpelea
  • Re: PR #20686 — Introducing a Zephyr-based Bluetooth host stack under net/bt: background, technical motivation, and proposed evolution plan chao an
  • Re: PR #20686 — Introducing a Zephyr-based Bluetooth host stack under net/bt: background, technical motivation, and proposed evolution plan Tomek CEDRO
  • Re: PR #20686 — Introducing a Zephyr-based Bluetooth host stack under net/bt: background, technical motivation, and proposed evolution plan chao an
  • Re: PR #20686 — Introducing a Zephyr-based Bluetooth host stack under net/bt: background, technical motivation, and proposed evolution plan Alan C. Assis
  • Re: PR #20686 — Introducing a Zephyr-based Bluetooth host stack under net/bt: background, technical motivation, and proposed evolution plan chao an
  • Re: PR #20686 — Introducing a Zephyr-based Bluetooth host stack under net/bt: background, technical motivation, and proposed evolution plan Alan C. Assis
  • Re: PR #20686 — Introducing a Zephyr-based Bluetooth host stack under net/bt: background, technical motivation, and proposed evolution plan chao an
  • Re: PR #20686 — Introducing a Zephyr-based Bluetooth host stack under net/bt: background, technical motivation, and proposed evolution plan Alan C. Assis
  • Re: PR #20686 — Introducing a Zephyr-based Bluetooth host stack under net/bt: background, technical motivation, and proposed evolution plan chao an
  • Re: PR #20686 — Introducing a Zephyr-based Bluetooth host stack under net/bt: background, technical motivation, and proposed evolution plan Alan C. Assis
  • Re: PR #20686 — Introducing a Zephyr-based Bluetooth host stack under net/bt: background, technical motivation, and proposed evolution plan chao an
  • Re: PR #20686 — Introducing a Zephyr-based Bluetooth host stack under net/bt: background, technical motivation, and proposed evolution plan Alan C. Assis
  • Re: PR #20686 — Introducing a Zephyr-based Bluetooth host stack under net/bt: background, technical motivation, and proposed evolution plan chao an
  • Re: PR #20686 — Introducing a Zephyr-based Bluetooth host stack under net/bt: background, technical motivation, and proposed evolution plan Alan C. Assis
  • Re: PR #20686 — Introducing a Zephyr-based Bluetooth host stack under net/bt: background, technical motivation, and proposed evolution plan Tomek CEDRO
  • Re: PR #20686 — Introducing a Zephyr-based Bluetooth host stack under net/bt: background, technical motivation, and proposed evolution plan chao an
  • Re: PR #20686 — Introducing a Zephyr-based Bluetooth host stack under net/bt: background, technical motivation, and proposed evolution plan chao an
  • Re: PR #20686 — Introducing a Zephyr-based Bluetooth host stack under net/bt: background, technical motivation, and proposed evolution plan Alin Jerpelea
  • Re: PR #20686 — Introducing a Zephyr-based Bluetooth host stack under net/bt: background, technical motivation, and proposed evolution plan chao an
• Looking for help with merging patches for AVR kr . git
  • Re: Looking for help with merging patches for AVR Felipe Moura Oliveira
  • Re: Looking for help with merging patches for AVR Swatantra
  • Re: Looking for help with merging patches for AVR Swatantra
  • Re: Looking for help with merging patches for AVR Alin Jerpelea
  • Re: Looking for help with merging patches for AVR Alin Jerpelea
  • Re: Looking for help with merging patches for AVR Abhishek Mishra
  • Re: Looking for help with merging patches for AVR kr . git
  • Re: Looking for help with merging patches for AVR Swatantra
  • Re: Looking for help with merging patches for AVR kr . git

• Earlier messages