Re: [linux-yocto] Seeking information on use of linux-yocto-dev

2024-04-28 Thread Sourabh Banerjee (QUIC) 



> -Original Message-
> From: Ross Burton 
> Sent: Wednesday, April 24, 2024 4:30 PM
> To: Sourabh Banerjee (QUIC) 
> Cc: Bruce Ashfield ; linux-
> yo...@lists.yoctoproject.org
> Subject: Re: [linux-yocto] Seeking information on use of linux-yocto-dev
> 
> WARNING: This email originated from outside of Qualcomm. Please be wary of
> any links or attachments, and do not enable macros.
> On 23 Apr 2024, at 17:33, Sourabh Banerjee (QUIC)
>  wrote:
> 
> 2. Is linux-yocto-dev tested by the autobuilder or a similar CI?
> 
> We've had adding it to the autobuilder CI on the wishlist for quite a while. I
> thought
> Ross added something a few months ago, but I can't recall the details. We do
> need
> to decide on exactly what to test, making sure it is lighter than what is run
> against
> the release kernels that I generate.
> 
> If it was in CI there might be some breakage due to the bleeding edge nature 
> of
> the updates. We just wouldn't want it to block any project milestones if run 
> as
> part of CI.
> 
> Added Ross to get a bit more clarity on autobuilder setup to linux-yocto-dev.
> 
> The public autobuilder doesn’t -- yet -- do linux-yocto-dev builds.  Mainly
> because it would need to be ran separately as it does break more than the 
> stable
> kernels so would need to be monitored by a human but not impact the existing
> builds, and the extra load on the AB would ideally be balanced out by some
> other changes so the net change is zero.

For the builds that Autobuilder runs how are the test cases run?
Does AB support any remote test invocation, such that the artifacts created by
Autobuilder are sent to a remotely connected device to be tested?

> 
> Our meta-arm CI does do builds with linux-yocto-dev, and we find new
> regressions or failures every few weeks or so. It fails enough due to upstream
> churn that we tell it to consider failures in linux-yocto-dev to be warnings 
> not
> errors…

I suppose this is meta-arm CI at some ARM location? And it different from the 
meta-arm CI in AB?
Is this CI just a build or a it runs a test as well?

> 
> Ross

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13879): 
https://lists.yoctoproject.org/g/linux-yocto/message/13879
Mute This Topic: https://lists.yoctoproject.org/mt/105677861/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] [yocto-autobuilder-helper] config-json: use quillback branch for meta-agl

2024-04-28 Thread Steve Sakoman 
kirkstone is no longer supported on master branch

Signed-off-by: Steve Sakoman 
---
 config.json | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/config.json b/config.json
index 60fe6a4..cc6d45c 100644
--- a/config.json
+++ b/config.json
@@ -1284,7 +1284,7 @@
 },
 "meta-agl": {
 "url" : "https://git.automotivelinux.org/AGL/meta-agl;,
-"branch" : "master",
+"branch" : "quillback",
 "revision" : "HEAD",
 "no-layer-add" : true
 },
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#63007): https://lists.yoctoproject.org/g/yocto/message/63007
Mute This Topic: https://lists.yoctoproject.org/mt/105782483/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[linux-yocto] Trial merge of v5.15.157 v6.1.88 v6.6.29 for linux-yocto

2024-04-28 Thread Kevin Hao 
Hi Bruce,

This is a trial merge of the stable kernel v5.15.157 v6.1.88 v6.6.29 for the 
following branches in the linux-yocto.
  c77673e7423a  v5.15/standard/sdkv5.10/axxia
  99cb138a69a5  v5.15/standard/preempt-rt/sdkv5.10/axxia
  d39c8ca540cb  v5.15/standard/base
  49d3fa750e2a  v5.15/standard/preempt-rt/base
  66ac9ee9006a  v5.15/standard/cn-sdkv5.4/octeon
  4d5df6f226c0  v5.15/standard/preempt-rt/cn-sdkv5.4/octeon
  93a37f0e56a8  v5.15/standard/cn-sdkv5.15/octeon
  758ac8d2fc96  v5.15/standard/preempt-rt/cn-sdkv5.15/octeon
  efb1432c522f  v5.15/standard/ti-sdk-5.10/ti-j72xx 
 #Have textual conflicts
  8fd8a06ad8e4  v5.15/standard/preempt-rt/ti-sdk-5.10/ti-j72xx  
 #Have textual conflicts
  dd2b963044cb  v5.15/standard/nxp-sdk-5.15/nxp-soc
  9efe7c5bcc42  v5.15/standard/preempt-rt/nxp-sdk-5.15/nxp-soc
  c5af99ba62f7  v5.15/standard/bcm-2xxx-rpi
  aa022a372c08  v5.15/standard/preempt-rt/bcm-2xxx-rpi
  cd04815df3a6  v5.15/standard/nxp-sdk-5.15/nxp-s32g
  8323749608ac  v5.15/standard/preempt-rt/nxp-sdk-5.15/nxp-s32g
  755e381fe568  v5.15/standard/intel-sdk-5.15/intel-socfpga
  0a488a43808d  v5.15/standard/preempt-rt/intel-sdk-5.15/intel-socfpga
  da777bf7cf98  v5.15/standard/x86
  f7cce3c911db  v5.15/standard/preempt-rt/x86
  8e6fdc870f6d  v5.15/standard/sdkv5.15/xlnx-soc
  a2a6a897fd92  v5.15/standard/preempt-rt/sdkv5.15/xlnx-soc
  4433912902ca  v6.1/standard/sdkv5.10/axxia
  534ef5a56db3  v6.1/standard/preempt-rt/sdkv5.10/axxia
  17f9487103d6  v6.1/standard/base
  c912215ee8d4  v6.1/standard/preempt-rt/base
  40db16f5f901  v6.1/standard/ti-sdk-6.1/ti-j7xxx
  16725e65c801  v6.1/standard/preempt-rt/ti-sdk-6.1/ti-j7xxx
  95646c56091f  v6.1/standard/nxp-sdk-6.1/nxp-soc
  bb8eabca5a8c  v6.1/standard/preempt-rt/nxp-sdk-6.1/nxp-soc
  18ff609873d9  v6.1/standard/cn-sdkv5.15/octeon
  356001e9c70a  v6.1/standard/preempt-rt/cn-sdkv5.15/octeon
  75c8cf78c2b3  v6.1/standard/cn-sdkv6.1/octeon
  c73a187227a3  v6.1/standard/preempt-rt/cn-sdkv6.1/octeon
  186e1e39374c  v6.1/standard/microchip-polarfire-soc
  6d9de798e181  v6.1/standard/preempt-rt/microchip-polarfire-soc
  7c23e4e67054  v6.1/standard/bcm-2xxx-rpi  
 #Have textual conflicts
  7e10d8c563ab  v6.1/standard/preempt-rt/bcm-2xxx-rpi   
 #Have textual conflicts
  ca35e771af6f  v6.1/standard/nxp-sdk-5.15/nxp-s32g
  a13bffccb8c6  v6.1/standard/preempt-rt/nxp-sdk-5.15/nxp-s32g
  bfab1370f344  v6.1/standard/intel-sdk-6.1/intel-socfpga
  3ec9a0c52b1d  v6.1/standard/preempt-rt/intel-sdk-6.1/intel-socfpga
  9001dae7c9e5  v6.1/standard/x86
  479a65350dfd  v6.1/standard/preempt-rt/x86
  c2c0dfa58c76  v6.1/standard/sdkv6.1/xlnx-soc
  8b1cf59c4b59  v6.1/standard/preempt-rt/sdkv6.1/xlnx-soc
  34435ec6dae2  v6.6/standard/base
  664ecd92e654  v6.6/standard/preempt-rt/base   
 #Have textual conflicts
  85ac62a6fdc6  v6.6/standard/nxp-sdk-6.6/nxp-soc
  488f3e2ba691  v6.6/standard/preempt-rt/nxp-sdk-6.6/nxp-soc
 #Have textual conflicts

- One trivial merge conflict on v5.15 j7xx and v6.1 rpi branches respectively.
- Several annoying conflicts on v6.6 rt kernel.

All the branches have passed my build test. I have pushed all these branches to:
https://github.com/haokexin/linux

You can use this as a reference for the linux-yocto stable kernel bump.

Thanks,
Kevin

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13878): 
https://lists.yoctoproject.org/g/linux-yocto/message/13878
Mute This Topic: https://lists.yoctoproject.org/mt/105779483/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[linux-yocto] drm/bridge: adv7511: Fix incorrect merge conflict resolutions in adv7511_probe()

2024-04-28 Thread Kevin Hao 
From: Kevin Hao 

When merging b140d9d4515f ("drm/bridge: adv7511: fix crash on irq during
probe") into nxp branches, it conflicts with the SDK commit ad93dd09fbbe
("Revert "drm/bridge: adv7511: Register and attach our DSI device at
probe""). The current merge resolutions introduced two issues:
- Part of codes deleted by SDK commit was restored mistakenly.
- Reference of the label deleted by SDK commit.

Resolve them to fix the build errors.

Signed-off-by: Kevin Hao 
---
Hi Bruce,

Please help me merge this into the following two branches:
  v6.1/standard/nxp-sdk-6.1/nxp-soc
  v6.1/standard/preempt-rt/nxp-sdk-6.1/nxp-soc

 drivers/gpu/drm/bridge/adv7511/adv7511_drv.c | 8 +---
 1 file changed, 1 insertion(+), 7 deletions(-)

diff --git a/drivers/gpu/drm/bridge/adv7511/adv7511_drv.c 
b/drivers/gpu/drm/bridge/adv7511/adv7511_drv.c
index 6e90871267f1..aba1fea6c22c 100644
--- a/drivers/gpu/drm/bridge/adv7511/adv7511_drv.c
+++ b/drivers/gpu/drm/bridge/adv7511/adv7511_drv.c
@@ -1422,13 +1422,7 @@ static int adv7511_probe(struct i2c_client *i2c, const 
struct i2c_device_id *id)
IRQF_ONESHOT, dev_name(dev),
adv7511);
if (ret)
-   goto err_unregister_audio;
-   }
-
-   if (adv7511->type == ADV7533 || adv7511->type == ADV7535) {
-   ret = adv7533_attach_dsi(adv7511);
-   if (ret)
-   goto err_unregister_audio;
+   goto err_unregister_cec;
}
 
return 0;
-- 
2.44.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13877): 
https://lists.yoctoproject.org/g/linux-yocto/message/13877
Mute This Topic: https://lists.yoctoproject.org/mt/105779474/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-