net: if: Fix NET_DEVICE_DT_DEFINE_INSTANCE macro

.checkpatch.conf

@@ -28,4 +28,5 @@
 --ignore COMPLEX_MACRO
 --ignore MULTISTATEMENT_MACRO_USE_DO_WHILE
 --ignore ENOSYS
+--ignore IS_ENABLED_CONFIG
 --exclude ext

.editorconfig

@@ -9,7 +9,7 @@ charset = utf-8
 end_of_line = lf
 insert_final_newline = true
 trim_trailing_whitespace = true
-max_line_length = 80
+max_line_length = 100
 
 # Assembly
 [*.S]
@@ -21,6 +21,16 @@ indent_size = 8
 indent_style = tab
 indent_size = 8
 
+# C++
+[*.{cpp,hpp}]
+indent_style = tab
+indent_size = 8
+
+# Linker Script
+[*.ld]
+indent_style = tab
+indent_size = 8
+
 # Python
 [*.py]
 indent_style = space
@@ -31,6 +41,11 @@ indent_size = 4
 indent_style = tab
 indent_size = 8
 
+# reStructuredText
+[*.rst]
+indent_style = space
+indent_size = 3
+
 # YAML
 [*.{yml,yaml}]
 indent_style = space
@@ -60,6 +75,7 @@ indent_size = 2
 # Makefile
 [Makefile]
 indent_style = tab
+indent_size = 8
 
 # Device tree
 [*.{dts,dtsi,overlay}]
@@ -68,8 +84,9 @@ indent_size = 8
 
 # Git commit messages
 [COMMIT_EDITMSG]
-max_line_length = 72
+max_line_length = 75
 
 # Kconfig
 [Kconfig*]
-indent_style=tab
+indent_style = tab
+indent_size = 8

.gitattributes

@@ -4,6 +4,10 @@
 .gitignore export-ignore
 .mailmap export-ignore
 
+# Tell git to not diff certain files
+*.svg -diff
+
 # Tell linguist that generated test pattern files should not be included in the
 # language statistics.
-*.pat linguist-generated=true
+*.pat linguist-generated
+*.svg linguist-generated

.github/ISSUE_TEMPLATE/bug_report.md

@@ -9,7 +9,12 @@ assignees: ''
 
 **Describe the bug**
 A clear and concise description of what the bug is.
-What have you tried to diagnose or workaround this issue?
+
+Please also mention any information which could help others to understand
+the problem you're facing:
+ - What target platform are you using?
+ - What have you tried to diagnose or workaround this issue?
+ - ...
 
 **To Reproduce**
 Steps to reproduce the behavior:
@@ -35,6 +40,6 @@ explain the issue. (if unable to obtain text log, add a screenshot)
  - Toolchain (e.g Zephyr SDK, ...)
  - Commit SHA or Version used
 
-
 **Additional context**
-Add any other context about the problem here.
+Add any other context that could be relevant to your issue, such as pin setting,
+target configuration, ...

.github/ISSUE_TEMPLATE/ext-source.md

@@ -18,7 +18,7 @@ Brief description of what this software does
 
 ## Mode of integration
 
-Describe whether you'd like to integrate this exernal component in the main tree
+Describe whether you'd like to integrate this external component in the main tree
 or as a module, and why. If the mode of integration is a module, suggest a
 repository name for the module
 

.github/ISSUE_TEMPLATE/feature_request.md

@@ -2,7 +2,7 @@
 name: Feature request
 about: Suggest an idea for this project
 title: ''
-labels: feature request
+labels: Feature Request
 assignees: ''
 
 ---

.github/ISSUE_TEMPLATE/nomination.md

@@ -0,0 +1,41 @@
+---
+name: Contributor Nomination
+about: Nominate a GitHub user for additional rights on the Zephyr Project
+title: ''
+labels: Role Nomination
+assignees: ''
+
+---
+
+# Background
+
+The [TSC Project Roles] defines the main roles for the Zephyr Project, including
+Maintainer, Collaborator, and Contributor.
+
+By default anyone that contributes code or documentation is a Contributor, but
+with the lowest [GitHub Permission Level] of Read. For example, Contributors
+with Read permission do not have the permission to add reviewers to a pull
+request.
+
+Use this template to nominate a GitHub user for an elevated permission level in
+the Contributor role.
+
+# Nomination
+
+## GitHub User
+
+Provide the following information about the GitHub user:
+
+1. Full Name
+1. GitHub username
+1. Organization (optional)
+
+## Supporting Documents
+
+Add links to 3-5 GitHub pull requests, in the Zephyr project, authored or
+reviewed by the GitHub user that demonstrate the user's dedication to the
+Zephyr project.
+
+
+[TSC Project Roles]: <https://docs.zephyrproject.org/latest/project/project_roles.html>
+[GitHub Permission Level]: <https://docs.github.com/en/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization>

.github/SECURITY.md

@@ -8,12 +8,12 @@ updates:
   - The most recent release, and the release prior to that.
   - Active LTS releases.
 
-At this time, with the latest release of v2.5.0, the supported
+At this time, with the latest release of v3.0.0, the supported
 versions are:
 
-  - 1.14.2: Current LTS
-  - v2.4.0: Prior release
-  - v2.5.0: Current release
+  - v2.7.0: Current LTS
+  - v2.7.0: Prior release
+  - v3.0.0: Current release
 
 ## Reporting process