Skip to content

linux-qcom: specify dummy revision for devupstream #1560

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.

Sign up for GitHub

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

Open
anujm1 wants to merge 1 commit into
base: master
Choose a base branch
from
Open

linux-qcom: specify dummy revision for devupstream #1560

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion recipes-kernel/linux/linux-qcom-next_git.bb
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,9 @@ SRC_URI += " \
# virtual/kernel provider to 'linux-qcom-next-upstream'
BBCLASSEXTEND = "devupstream:target"
PN:class-devupstream = "linux-qcom-next-upstream"
SRCREV:class-devupstream ?= "${AUTOREV}"

# Pin this to the qcom-next-6.19-rc6-20260207, override this in local.conf
SRCREV:class-devupstream ?= "ccc1345fb4742e377d7d89658efe085c62c25164"
Copy link
Contributor

@lumag lumag Feb 13, 2026

Choose a reason for hiding this comment

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

This should be using something like linux-yocto-dev:

SRCREV ?= '${@oe.utils.conditional("PREFERRED_PROVIDER_virtual/kernel", "linux-qcom-next-upstream", "${AUTOREV}", "29594404d7fe73cd80eaa4ee8c43dcc53970c60e", d)}'

(yes, 3.7 was a good kernel)

Copy link
Contributor Author

@anujm1 anujm1 Feb 13, 2026

Choose a reason for hiding this comment

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

For an offline build with linux-qcom-next-upstream, it would still require a user to add an entry in local.conf to override SRCREV. So, does this approach offer any advantage?

linux-yocto-dev does not inherit devupstream while all others inheriting it expect users to override SRCREV in local.conf so it offers a consistent behaviour.

Copy link
Contributor

@lumag lumag Feb 13, 2026

Choose a reason for hiding this comment

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

I find it wasier to switch PREFERRED_PROVIDER in local.conf than switching provider and setting the AUTOREV.


S = "${UNPACKDIR}/${BP}"

Expand Down
4 changes: 3 additions & 1 deletion recipes-kernel/linux/linux-qcom_6.18.bb
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,9 @@ SRC_URI += " \
# virtual/kernel provider to 'linux-qcom-6.18.y-upstream'
BBCLASSEXTEND = "devupstream:target"
PN:class-devupstream = "linux-qcom-6.18.y-upstream"
SRCREV:class-devupstream ?= "${AUTOREV}"

# Pin this to the qcom-6.18.y-20260207, override this in local.conf
SRCREV:class-devupstream ?= "93be04f5fe1314eafb3293abc558e8ade4e8d2bb"

S = "${UNPACKDIR}/${BP}"

Expand Down
Loading