forked from armbian/build
-
-
Notifications
You must be signed in to change notification settings - Fork 0
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
[pull] main from armbian:main #30
Open
pull
wants to merge
967
commits into
mir-one:main
Choose a base branch
from
armbian:main
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
documentation
Improvements or additions to documentation
Desktop
labels
Aug 18, 2024
First of all, we make changes to the core functions and only then we change the device tree
Here, a folder named patches.addon must exist in order for users to add new patches. These patches will be applied but they are awaiting more careful consideration. Let's just sort the sequence a little bit.
It will be useful for us to receive the trace stack from users.
Add the missing fixes from #7568 and re-extracted the patches.
…ools. In order for the cleanup to be correct for tools, we need to pass the VMLINUX_BTF variable, which contains the real path to the vmlinux file we just compiled. The vmlinux file itself is not involved in cleaning, but the Makefile checks for its presence and cleaning is aborted if it is not found.
- this affects `rewrite-kernel-config` and `kernel-config` CLIs - this does not actually change the .config's we have, that will happen later / gradually as configs are rewritten - no more `.defconfig` files are produced (they were in gitignore)
Signed-off-by: Andy Yan <[email protected]>
This reverts commit e5b5e11.
This reverts commit b17e9e5.
…FIG_CFG80211=m` and `CONFIG_MAC80211=m` on 6.13+ - we need to run the hooks _before_ running oldconfig, otherwise it is too late - drop `kernel_config_check_and_repair()` since it won't ever detect anything now
- Fixes dc558d7 which forgot the patches
- seems upstream has gone `remove` -> `remove_new` and back to `remove` now
In the current main branch, workflow update-tools includes the content of the upstream release notes in the created GitHub Issue. This triggers a notification to every upstream contributor mentioned in the release note. This also creates a cross-reference link to our GitHub Issue (reporting that our dependency is not up-to-date) in every upstream issue and pull request. The information that we need to update our dependency is not relavant to the upstream contributors, issues, and pull requests at all. We should avoid this situation. In the first place, we do not need to include a copy of the upstream release note. We can just put a link to the upstream release note. Currently, we anyway hide the content in the <details> tag and require the reader to press the button. The user experience is not so different from pressing a link and visiting the upstream release note.
- `legacy` doesn't exist for a long while now
- `CONFIG_REISERFS` is no more - `CONFIG_CFG80211` required to keep wireless working (done via hooks)
Bumps [setuptools](https://github.com/pypa/setuptools) from 75.7.0 to 75.8.0. - [Release notes](https://github.com/pypa/setuptools/releases) - [Changelog](https://github.com/pypa/setuptools/blob/main/NEWS.rst) - [Commits](pypa/setuptools@v75.7.0...v75.8.0) --- updated-dependencies: - dependency-name: setuptools dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
⤵️ pull
BSP
Desktop
documentation
Improvements or additions to documentation
Framework
GitHub Actions
GitHub
Hardware
Patches
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by pull[bot]
Can you help keep this open source service alive? 💖 Please sponsor : )