Skip to content

Conversation

@jerpelea
Copy link
Contributor

Summary

included
#15309
#15328
#15350

Impact

RELEASE

Testing

CI

hujun260 and others added 3 commits December 27, 2024 11:02
CC:  pthread/pthread_exit.c common/espressif/esp_lowputc.c: In function 'esp_lowputc_disable_all_uart_int':
common/espressif/esp_lowputc.c:215:29: error: passing argument 1 of 'spin_lock_irqsave' discards 'const' qualifier from pointer target type [-Werror=discarded-qualifiers]
  215 |   flags = spin_lock_irqsave(&priv->lock);
      |                             ^~~~~~~~~~~
In file included from common/espressif/esp_lowputc.c:40:
/home/hujun5/下载/vela_sim/nuttx/include/nuttx/spinlock.h:511:55: note: expected 'volatile spinlock_t *' {aka 'volatile unsigned int *'} but argument is of type 'const spinlock_t *' {aka 'const unsigned int *'}
  511 | irqstate_t spin_lock_irqsave(FAR volatile spinlock_t *lock)
      |                                  ~~~~~~~~~~~~~~~~~~~~~^~~~
common/espressif/esp_lowputc.c:232:26: error: passing argument 1 of 'spin_unlock_irqrestore' discards 'const' qualifier from pointer target type [-Werror=discarded-qualifiers]
  232 |   spin_unlock_irqrestore(&priv->lock, flags);
      |                          ^~~~~~~~~~~
/home/hujun5/下载/vela_sim/nuttx/include/nuttx/spinlock.h:674:54: note: expected 'volatile spinlock_t *' {aka 'volatile unsigned int *'} but argument is of type 'const spinlock_t *' {aka 'const unsigned int *'}
  674 | void spin_unlock_irqrestore(FAR volatile spinlock_t *lock,

Signed-off-by: hujun5 <hujun5@xiaomi.com>
…re possible, and otherwise defined macros using built-ins to allow the 802.11 header to compile on Arch Linux where cpu_to_le16, le32_to_cpu and hweight8 definitions were missing.
Signed-off-by: wangmingrong1 <wangmingrong1@xiaomi.com>
@github-actions github-actions bot added Arch: risc-v Issues related to the RISC-V (32-bit or 64-bit) architecture Area: Drivers Drivers issues Size: M The size of the change in this PR is medium labels Dec 27, 2024
@nuttxpr
Copy link

nuttxpr commented Dec 27, 2024

[Experimental Bot, please feedback here]

Fill In The Commit Message: This PR contains a Commit with an Empty Commit Message. Please fill in the Commit Message with the PR Summary.

This PR appears to partially meet the NuttX requirements. While it references related PRs and indicates a RELEASE impact, it's missing crucial information.

Here's what's lacking:

  • Summary: While the PR links are provided, a concise summary describing the changes within this PR is missing. What is the overall goal of these combined changes? What functionality is affected?
  • Impact: "RELEASE" is insufficient. While it implies a significant impact, it doesn't detail the specific impact. Does it introduce a new feature? Change existing behavior? Affect specific architectures or boards? All impact categories (user, build, hardware, documentation, security, compatibility) should be addressed with "YES/NO" and descriptions where applicable.
  • Testing: "CI" is not enough. While Continuous Integration is important, the PR needs to show specific testing results. Provide examples of commands used and output logs before and after the change to demonstrate the fix or new functionality. What specific targets were tested?

Therefore, the PR needs more details to fully meet the requirements. The author should expand on the Summary, Impact, and Testing sections to provide the missing information.

@github-actions github-actions bot added the Area: OS Components OS Components issues label Dec 27, 2024
@xiaoxiang781216 xiaoxiang781216 merged commit 549a86c into apache:releases/12.8 Dec 28, 2024
25 of 27 checks passed
@jerpelea jerpelea deleted the bp-15350 branch December 28, 2024 08:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Arch: risc-v Issues related to the RISC-V (32-bit or 64-bit) architecture Area: Drivers Drivers issues Area: OS Components OS Components issues Size: M The size of the change in this PR is medium

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants