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

linux-lxatac: Add three patches to fix QA Issues #106

Merged
merged 1 commit into from
Feb 15, 2024

Conversation

ukleinek
Copy link

This fixes:

WARNING: linux-lxatac-6.7-r0 do_package_qa: QA Issue: File /usr/src/debug/linux-lxatac/6.7-r0/arch/arm/include/generated/asm/mach-types.h in package linux-lxatac-src contains reference to TMPDIR
File /usr/src/debug/linux-lxatac/6.7-r0/drivers/tty/vt/consolemap_deftbl.c in package linux-lxatac-src contains reference to TMPDIR
File /usr/src/debug/linux-lxatac/6.7-r0/lib/oid_registry_data.c in package linux-lxatac-src contains reference to TMPDIR [buildpaths]

This fixes:

	WARNING: linux-lxatac-6.7-r0 do_package_qa: QA Issue: File /usr/src/debug/linux-lxatac/6.7-r0/arch/arm/include/generated/asm/mach-types.h in package linux-lxatac-src contains reference to TMPDIR
	File /usr/src/debug/linux-lxatac/6.7-r0/drivers/tty/vt/consolemap_deftbl.c in package linux-lxatac-src contains reference to TMPDIR
	File /usr/src/debug/linux-lxatac/6.7-r0/lib/oid_registry_data.c in package linux-lxatac-src contains reference to TMPDIR [buildpaths]

Signed-off-by: Uwe Kleine-König <uwe@kleine-koenig.org>
Copy link
Member

@hnez hnez left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great, fewer reference to TMPDIR warnings when compiling Linux!
We are not yet down to zero due to perf, but some day we will get there.

Thanks

@hnez hnez merged commit da87d96 into linux-automation:nanbield Feb 15, 2024
2 checks passed
@ejoerns
Copy link
Collaborator

ejoerns commented Feb 15, 2024

Great, fewer reference to TMPDIR warnings when compiling Linux! We are not yet down to zero due to perf, but some day we will get there.

FTR: We have a working fix for perf, but still discussing if this is sufficient or requires a broader approach to fix perf python handling

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants