On 6/20/23 09:03, Xavier Drudis Ferran wrote:
El Tue, Jun 20, 2023 at 02:50:48AM +0200, Marek Vasut deia:
On 6/13/23 08:52, Xavier Drudis Ferran wrote:
U-Boot TPL 2023.07-rc2-00144-g497967f1ee (Jun 12 2023 - 11:15:47)
Next is already at rc4 , what's this rc2 ?
It's a test I did last week (June 12th). What do you think has changed
in next between rc2 and rc4 so that this shouldn't happen now ?
The beginning of the email states:
"
Ok. New test.
This uses yesterday morning's next branch.
commit 5b589e139620214f
"
So, that is not the case ?
Also, commit 497967f1ee does not exist in upstream U-Boot, was this some
patched U-Boot tree ?
My last patch (sent yesterday) was tested with the next branch as of
yesterday morning. But you can test it yourself with any version you like.
Do I have to send the logs of each test I do to the list every time ?
Ideally the claims you make about what you tested and logs from the test
should match, that would be a good starting point.
I thought Simon Glass reply last week to the mail you quoted already
showed agreement that the issue exists, and the adding of the
UCLASS_BOOTDEV device is per design, so cmd/usb.c needs fixing to deal
with this change.
I am not disputing that. What bothers me is the still missing consistent
test case, esp. if this is a fix which should be added this late in release.
