Re: [SPAM] [PATCH v5 00/14] Support PCIe RC to AST2600 and AST2700

["Cédric Le Goater" <clg@redhat.com>]

On 10/1/25 04:20, Jamin Lin wrote:
> Hi Cédric
> 
>> Subject: Re: [SPAM] [PATCH v5 00/14] Support PCIe RC to AST2600 and
>> AST2700
>>
>> On 9/19/25 11:29, Jamin Lin wrote:
>>> v1:
>>>    1. Add PCIe PHY, CFG, and MMIO window support for AST2600.
>>>       Note: Only supports RC_H.
>>>    2. Add PCIe PHY, CFG, and MMIO window support for AST2700.
>>>       Note: Supports 3 RCs.
>>>
>>> v2:
>>>     1. Introduce a new root port device.
>>>     2. For AST2600 RC_H, add the root device at 80:00.0 and a root port at
>> 80.08.0
>>>        to match the real hardware topology, allowing users to attach PCIe
>> devices
>>>        at the root port.
>>>     3. For AST2700, add a root port at 00.00.0 for each PCIe root complex to
>> match
>>>        the real hardware topology, allowing users to attach PCIe devices at
>> the
>>>        root port.
>>>
>>> v3:
>>>     1. Fix review issues.
>>>     2. update functional test for the e1000e network card.
>>>     3. update license header
>>>     4. Adding "Based on previous work from Cedric Le Goater, with Jamin's
>> summary
>>>        implementation.
>>>
>>> v4:
>>>     1. Initialize pointers to NULL when declaring them.
>>>     2. Use distinct variable names to resolve memory leak issues.
>>>     3. Update functional tests to verify assigned IP addresses from
>>>        Intel NIC Ethernet interfaces.
>>>     4. Introduce pcie_mmio_alias in AspeedSoCState instead of dynamically
>>>        allocating memory.
>>>
>>> v5:
>>>     1. fix memory leak issue. Replace g_autofree with array.
>>>
>> Applied to aspeed-next.
>>
> 
> I saw that this patch series has been merged into master, but it looks like this particular patch was missed:
> https://patchwork.kernel.org/project/qemu-devel/patch/20250919093017.338309-15-jamin_lin@aspeedtech.com/
> [v5,14/14] tests/functional/aarch64/aspeed_ast2700: Add PCIe and network tests
> 
> Could you please help check on this?

my fault. I'll include it in the next PR. Sorry about that.

C.