dev  

Messages by Thread

• [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 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
• 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 Marco C.
• 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
  • Re: Looking for help with merging patches for AVR Swatantra
  • 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
  • Re: Looking for help with merging patches for AVR Swatantra
  • Re: Looking for help with merging patches for AVR Tomek CEDRO
  • Re: Looking for help with merging patches for AVR Tomek CEDRO
  • Re: Looking for help with merging patches for AVR kr . git
  • Re: Looking for help with merging patches for AVR Tomek CEDRO
  • 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
  • Re: Looking for help with merging patches for AVR Swatantra
  • Re: Looking for help with merging patches for AVR kr . git
• [PR] device/serial: reopen the port after USB re-enumeration [nuttx-ntfc] via GitHub
  • Re: [PR] device/serial: reopen the port after USB re-enumeration [nuttx-ntfc] via GitHub
• [PR] Busyloop idle prompt [nuttx-ntfc] via GitHub
• [PR] core: refuse commands longer than the target line buffer [nuttx-ntfc] via GitHub
  • Re: [PR] core: refuse commands longer than the target line buffer [nuttx-ntfc] via GitHub
• [PR] add resource leak detection fixture [nuttx-ntfc] via GitHub
• [PR] collector: add exclude_test to session.json [nuttx-ntfc] via GitHub
  • Re: [PR] collector: add exclude_test to session.json [nuttx-ntfc] via GitHub
• [PR] fix long and slow commands [nuttx-ntfc] via GitHub
  • Re: [PR] fix long and slow commands [nuttx-ntfc] via GitHub
• [DISCUSS] CI: keep the ccache of each build job, warmed on master Marco C.
  • [DISCUSS] CI: keep the ccache of each build job, warmed on master Marco C.
• [DISCUSS] Plain names that NuttX public headers define in every program Marco C.
  • Re: [DISCUSS] Plain names that NuttX public headers define in every program Xiang Xiao
  • Re: [DISCUSS] Plain names that NuttX public headers define in every program jlaitin0
• [DISCUSS] arm64 loader: erratum 843419 fix fails for big modules Marco C.
• Problem building Documentation (document isn't includes in any toctree) Peter Barada
• [DISCUSS] GOT relocations in relocatable ELF modules on arm64 Marco C.
• [DISCUSS] mmap(MAP_ANONYMOUS) does not return page-aligned memory Marco C.
  • Re: [DISCUSS] mmap(MAP_ANONYMOUS) does not return page-aligned memory kr . git
  • Re: [DISCUSS] mmap(MAP_ANONYMOUS) does not return page-aligned memory Xiang Xiao
  • Re: [DISCUSS] mmap(MAP_ANONYMOUS) does not return page-aligned memory Marco C.
  • Re: [DISCUSS] mmap(MAP_ANONYMOUS) does not return page-aligned memory kr . git

• Earlier messages