On 7/17/2024 2:44 PM, Patrick Robb wrote:
> On Mon, Jul 15, 2024 at 10:38 PM zhoumin wrote:
>>
>> Hi Patrick,
>>
>> Thanks for giving the link of commit `a6c3ec342ee1`.
>>
>> However I cannot checkout this commit in the next-net repository because
>> the commit ID is not exist in the history of ne
On Mon, Jul 15, 2024 at 10:38 PM zhoumin wrote:
>
> Hi Patrick,
>
> Thanks for giving the link of commit `a6c3ec342ee1`.
>
> However I cannot checkout this commit in the next-net repository because
> the commit ID is not exist in the history of next-net repository. Could
> you find it?
>
> It seem
Hi Patrick,
Thanks for giving the link of commit `a6c3ec342ee1`.
However I cannot checkout this commit in the next-net repository because
the commit ID is not exist in the history of next-net repository. Could
you find it?
It seems that the commit `a6c3ec342ee1` is nearly identical to the
c
Hi Min Zhou,
I am seeing that commit for next-net:
https://git.dpdk.org/next/dpdk-next-net/commit/?id=a6c3ec342ee105e322ffdb21e810cdfd38455c62
If you try to manually apply it on next-net, does it work?
Pasting the logs from our apply process below for context:
```
Trying to checkout branch: o
Hi Patrick,
Thanks for reminding me. The pw_maintainers_cli.py script indeed is
outdated in my fork.
I have updated this script, but still failed to apply this patch. I saw
all the other labs applied this patch based on commit of
'a6c3ec342ee105e322ffdb21e810cdfd38455c62', but I cannot find
Hello Zhoumin,
It looks like Loongarch CI failed to apply this patch, but it worked
at the other labs and locally for Serhii when they were checked out to
next-net.
Maybe your CI did not choose next-net, the right branch? I remember
you saying your CI is based on a fork of the dpdk-ci repo. Perha
Add initial ntnic ethdev skeleton and register PCI probe functions
Update documentation: Device description and feature list
Signed-off-by: Serhii Iliushyk
---
.mailmap | 1 +
MAINTAINERS| 7
doc/guides/nics/features/ntnic.ini
7 matches
Mail list logo