uapi: linux: xlnx-ai-engine: Fix leaked kernel configuration#3207
Merged
nunojsa merged 1 commit intoxlnx/release/linux-v6.12.y-2026r1from Mar 26, 2026
Merged
Conversation
This was already fixed in main, backported from xilinx tree [1]. But it looks like Xilinx did not backported this into their 6.12 2025.1 LTS release which means that our merge against that tag brought this issue again. [1]: dff948b Signed-off-by: Nuno Sá <nuno.sa@analog.com>
nunojsa
requested review from
CiprianRegus,
amiclaus,
btogorean,
buha,
chegbeli,
danmois,
dbogdan,
machschmitt,
mhennerich,
rbolboac and
stefpopa
as code owners
mhennerich
approved these changes
Mar 26, 2026
nunojsa
merged commit cc776ae
into
xlnx/release/linux-v6.12.y-2026r1
31 of 32 checks passed
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This was already fixed in main, backported from xilinx tree 1. But it looks like Xilinx did not backported this into their 6.12 2025.1 LTS release which means that our merge against that tag brought this issue again.
PR Description
necessary to understand them. List any dependencies required for this change.
any space), or simply check them after publishing the PR.
description and try to push all related PRs simultaneously.
PR Type
PR Checklist