review: Drop resolved upstream issues#34
Merged
Conversation
Lore follow-up comments are useful review evidence, but they can describe problems that the reviewed revision already fixes. Treating those comments as mandatory findings causes resolved review feedback to survive into the protected baseline and LKML report. Require the fast review to verify each upstream concern against the new code and complete series. Omit concerns that are conclusively addressed, while preserving lore provenance for defects that remain. Document the behavior and add regression assertions for both the general review prompt and rendered follow-up context. Signed-off-by: Andrea Righi <arighi@nvidia.com>
nirmoy
approved these changes
Jul 7, 2026
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.
Lore follow-up comments are useful review evidence, but they can describe problems that the reviewed revision already fixes. Treating those comments as mandatory findings causes resolved review feedback to survive into the protected baseline and LKML report.
Require the fast review to verify each upstream concern against the new code and complete series. Omit concerns that are conclusively addressed, while preserving lore provenance for defects that remain. Document the behavior and add regression assertions for both the general review prompt and rendered follow-up context.