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

Use common prefix for Kconfig option names (EHM-18) #18

Open
3 tasks done
igrr opened this issue Nov 5, 2024 · 0 comments
Open
3 tasks done

Use common prefix for Kconfig option names (EHM-18) #18

igrr opened this issue Nov 5, 2024 · 0 comments
Labels
Status: Opened Issue is new

Comments

@igrr
Copy link
Member

igrr commented Nov 5, 2024

Checklist

  • Checked the issue tracker for similar issues to ensure this is not a duplicate.
  • Provided a clear description of your suggestion.
  • Included any relevant context or examples.

Issue or Suggestion Description

Currently at least several different prefixes for Kconfig option names are used ( CONFIG_ESP_HOSTED_, CONFIG_ESP_SDIO_, CONFIG_ESP_SPI_0, CONFIG_SLAVE_, CONFIG_IDF_SLAVE_).

For most components, we have a rule that there should be a common prefix which is related to the component name. We could rename Kconfig options and use sdkconfig.rename file to achieve backwards compatibility.

@espressif-bot espressif-bot added the Status: Opened Issue is new label Nov 5, 2024
@github-actions github-actions bot changed the title Use common prefix for Kconfig option names Use common prefix for Kconfig option names (EHM-18) Nov 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Opened Issue is new
Projects
None yet
Development

No branches or pull requests

2 participants