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.

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

53 merge #189

Merged
merged 246 commits into from
Sep 11, 2024
Merged

53 merge #189

merged 246 commits into from
Sep 11, 2024

Conversation

Jason2866
Copy link
Collaborator

No description provided.

Yuan Hong Hui and others added 30 commits August 2, 2024 15:10
Fixes call to `gptimer_start` in one of the examples
which includes extra second parameter `&alarm_config`,
when the function takes only one.

Mreges espressif#14310
- Support enhanced BLE TX power setting and getting
 - Fix BLE channel map update when latency is not zero
…estricted()

The vTaskPlaceOnEventListRestricted() did not use the correct macro when
exiting a kernel cirtical section. This does not affect the HW targets
but on the Linux port, this caused an issue as the critical nesting
count became negative, leading to deadlocks. This commit fixes the bug
and updates the linux port to prevent the nesting count from going
negative.
Lapshin and others added 27 commits September 6, 2024 18:27
…tion_v5.3' into 'release/v5.3'

docs: remove user guide for esp32-pico-kit related docs after migration (v5.3)

See merge request espressif/esp-idf!32781
fix(ble/bluedroid): Fixed memory out-of-bounds issue when parsing adv data (v5.3)

See merge request espressif/esp-idf!33023
docs(ble/bluedroid): Optimize BLE example for setting advertising data (v5.3)

See merge request espressif/esp-idf!32755
….3' into 'release/v5.3'

change(esp_pm): bypass cache access assertion when using ext0 or ext1(backport v5.3)

See merge request espressif/esp-idf!33142
fix(ulp): Add the missing extern "C" guard to ulp_lp_core_print.h (GitHub PR) (v5.3)

See merge request espressif/esp-idf!32833
test(freertos): Fixed flaky scheduling time test (v5.3)

See merge request espressif/esp-idf!32848
- Fixed BLE vendor HCI set scan perfer address command
- Support BLE vendor HCI get controller compile version command
- Support BLE scanning and initiating coexist
change(mqtt): Updte esp_mqtt submodule (v5.3)

See merge request espressif/esp-idf!32938
…se/v5.3'

fix(cmake): Fixed linker not supporting -warn_commons for linux target on MacOS (v5.3)

See merge request espressif/esp-idf!33052
Add i80 LCD support on ESP32P4 (v5.3)

See merge request espressif/esp-idf!33293
- Fixed BLE vendor HCI set scan perfer address command
- Support BLE vendor HCI get controller compile version command
- Fixed BLE util buffer free after controller reset
- Fixed assert when connection already exist and be connected again
…5.3'

fix(wifi): Add PSRAM failure fallback in WiFi Queue API's (backport v5.3)

See merge request espressif/esp-idf!33345
Fix a few comments codespell identified.
fix(mbedtls/port): fix codespell issues (GitHub PR) (v5.3)

See merge request espressif/esp-idf!33010
…5.3'

Bugfix/fix some esp32 host issues(Backport v5.3)

See merge request espressif/esp-idf!32681
…ase/v5.3'

fix(newlib): sbom: add CVE-2024-30949 to cve-exclude-list

See merge request espressif/esp-idf!33369
feat(efuse): Updates esp_efuse_get_pkg_ver (v5.3)

See merge request espressif/esp-idf!32931
… 'release/v5.3'

Support BLE scanning and initiating coexist on ESP32 (v5.3)

See merge request espressif/esp-idf!33385
Fixed some BLE bugs 240826 on ESP32C3 (8ce789b) (v5.3)

See merge request espressif/esp-idf!33389
Copy link

github-actions bot commented Sep 11, 2024

Warnings
⚠️

Some issues found for the commit messages in this PR:

  • the commit message " fix(bt): Update bt lib for ESP32-C3 and ESP32-S3(f583012)":
    • summary looks empty
    • type/action looks empty
  • the commit message "Delete components/wifi_provisioning directory":
    • summary looks empty
    • type/action looks empty
  • the commit message "Merge branch 'docs/delete_user_guides_three_esp32_dev_boards_v5.3' into 'release/v5.3'":
    • probably contains Jira ticket reference (M-2). Please remove Jira tickets from commit messages.
  • the commit message "Merge branch 'feat/newlib-add-sbom-exclude_cve-2024-30949' into 'release/v5.3'":
    • probably contains Jira ticket reference (2024-30949, CVE-2024). Please remove Jira tickets from commit messages.
  • the commit message "Merge branch 'feature/update-openocd-to-v0.12.0-esp32-20240821_v5.3' into 'release/v5.3'":
    • probably contains Jira ticket reference (32-20240821, 32-20240821). Please remove Jira tickets from commit messages.
  • the commit message "Tasmota changes":
    • summary looks empty
    • type/action looks empty
  • the commit message "change(esp_hw_support): reorder light/deep sleep test cases and wrapper with corresponding support macros":
    • summary appears to be too long
  • the commit message "change(mqtt): Update esp_mqtt submodule":
    • probably contains Jira ticket reference (IDFGH-12831, IDFGH-12829, IDFGH-12735, IDF-8883). Please remove Jira tickets from commit messages.
  • the commit message "ci(mmu): add unicore test":
    • summary looks too short
  • the commit message "docs: delete user guides of ESP32-DevKitC, ESP-WROVER-KIT and ESP32-PICO-DevKitM-2":
    • probably contains Jira ticket reference (M-2). Please remove Jira tickets from commit messages.
    • summary appears to be too long
  • the commit message "feat(bt):add pytest for classic bt example":
    • summary looks empty
    • type/action looks empty
  • the commit message "feat(tools): update openocd version to v0.12.0-esp32-20240821":
    • probably contains Jira ticket reference (32-20240821). Please remove Jira tickets from commit messages.
  • the commit message "fix(MMU): fixed mmap deadlock when using multicore app with unicore bootloader":
    • scope/component should be lowercase without whitespace, allowed special characters are _ / . , * - .
  • the commit message "fix(newlib): sbom: add CVE-2024-30949 to cve-exclude-list":
    • probably contains Jira ticket reference (CVE-2024). Please remove Jira tickets from commit messages.
  • the commit message "fix(nimble) Added change to handle linked om data at blufi layer":
    • summary looks empty
    • type/action looks empty

Please fix these commit messages - here are some basic tips:

  • follow Conventional Commits style
  • correct format of commit message should be: <type/action>(<scope/component>): <summary>, for example fix(esp32): Fixed startup timeout issue
  • allowed types are: change,ci,docs,feat,fix,refactor,remove,revert,test
  • sufficiently descriptive message summary should be between 20 to 72 characters and start with upper case letter
  • avoid Jira references in commit messages (unavailable/irrelevant for our customers)

TIP: Install pre-commit hooks and run this check when committing (uses the Conventional Precommit Linter).

⚠️ Please consider squashing your 246 commits (simplifying branch history).
⚠️ The Pull Request description is empty. Please provide a detailed description.
⚠️
	The **target branch** for this Pull Request **must be the default branch** of the project (`master`).

	If you would like to add this feature to a different branch, please state this in the PR description and we will consider it.
Messages
📖 This PR seems to be quite large (total lines of code: 25333), you might consider splitting it into smaller PRs

👋 Hello Jason2866, we appreciate your contribution to this project!


📘 Please review the project's Contributions Guide for key guidelines on code, documentation, testing, and more.

🖊️ Please also make sure you have read and signed the Contributor License Agreement for this project.

Click to see more instructions ...


This automated output is generated by the PR linter DangerJS, which checks if your Pull Request meets the project's requirements and helps you fix potential issues.

DangerJS is triggered with each push event to a Pull Request and modify the contents of this comment.

Please consider the following:
- Danger mainly focuses on the PR structure and formatting and can't understand the meaning behind your code or changes.
- Danger is not a substitute for human code reviews; it's still important to request a code review from your colleagues.
- Resolve all warnings (⚠️ ) before requesting a review from human reviewers - they will appreciate it.
- Addressing info messages (📖) is strongly recommended; they're less critical but valuable.
- To manually retry these Danger checks, please navigate to the Actions tab and re-run last Danger workflow.

Review and merge process you can expect ...


We do welcome contributions in the form of bug reports, feature requests and pull requests via this public GitHub repository.

This GitHub project is public mirror of our internal git repository

1. An internal issue has been created for the PR, we assign it to the relevant engineer.
2. They review the PR and either approve it or ask you for changes or clarifications.
3. Once the GitHub PR is approved, we synchronize it into our internal git repository.
4. In the internal git repository we do the final review, collect approvals from core owners and make sure all the automated tests are passing.
- At this point we may do some adjustments to the proposed change, or extend it by adding tests or documentation.
5. If the change is approved and passes the tests it is merged into the default branch.
5. On next sync from the internal git repository merged change will appear in this public GitHub repository.

Generated by 🚫 dangerJS against 1c72268

@Jason2866 Jason2866 merged commit c797215 into release/v5.3_ulp Sep 11, 2024
1 of 2 checks passed
@Jason2866 Jason2866 deleted the 53_merge branch September 11, 2024 08:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.