On 4/11/23 4:32 PM, Denys Dmytriyenko wrote:
On Tue, Apr 11, 2023 at 04:14:47PM -0500, Andrew Davis wrote:
On 4/11/23 2:51 PM, Denys Dmytriyenko wrote:
On Tue, Apr 11, 2023 at 12:40:36PM -0500, Andrew Davis via
lists.yoctoproject.org wrote:
Not sure if anyone is testing on this device with -next, but for
completeness add its defconfig.
Signed-off-by: Andrew Davis <[email protected]>
---
meta-ti-bsp/recipes-kernel/linux/linux-ti-next_git.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta-ti-bsp/recipes-kernel/linux/linux-ti-next_git.bb
b/meta-ti-bsp/recipes-kernel/linux/linux-ti-next_git.bb
index b540e508..62831c9c 100644
--- a/meta-ti-bsp/recipes-kernel/linux/linux-ti-next_git.bb
+++ b/meta-ti-bsp/recipes-kernel/linux/linux-ti-next_git.bb
@@ -20,6 +20,7 @@ PV = "6.1.0-rc1+git${SRCPV}"
Should PV/SRCREV be bumped past 6.1-rc1?
Someone should. But unless we automate then it will get stale again.
It could be part of the build automation scripts when we start -next
testing..
And it already is - Arago Distro branding-next AUTOREVs it:
https://git.yoctoproject.org/meta-arago/tree/meta-arago-distro/conf/distro/include/branding-next.inc#n4
It is done indirectly through the Distro/branding as recipes shouldn't default
to AUTOREV. You don't want bitbake to hit kernel.org everytime the recipe gets
parsed, even when you are not building it.
I know "next" will be getting stale very quickly and it's expected, but it may
be nice to get it updated now, since you are changing it anyway...
Sure, why not, will add a patch for v3
Andrew
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#16361):
https://lists.yoctoproject.org/g/meta-ti/message/16361
Mute This Topic: https://lists.yoctoproject.org/mt/98202850/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
