RE: [PATCH v7 0/8] Support GPIO for AST2700

Jamin Lin posted 8 patches 1 week ago
Only 0 patches received!
RE: [PATCH v7 0/8] Support GPIO for AST2700
Posted by Jamin Lin 1 week ago
Hi all,

> Subject: [PATCH v7 0/8] Support GPIO for AST2700
> 

I don't know why I send this patch series failed to the following email addresses and got the following errors.
open list:All patches CC here <qemu-devel@nongnu.org> 
open list:ASPEED BMCs <qemu-arm@nongnu.org>

2024/10/1 上午 06:43:04 - Server at nongnu.org (2001:470:142:3::10) returned '451 4.4.397 Error communicating with target host. -> 421 4.2.1 Unable to connect ->
SocketError: Failed to connect. Winsock error code: 10051, Win32 error code: 10051'

Do you encounter the same issue?
If no, I will re-send this patch series with Thomas reviewed tag in v8.

Thanks-Jamin

> v1: Support GPIO for AST2700
> v2: Fix clear incorrect interrupt status and adds reviewer suggestions
> v3: Remove nested conditionals and adds reviewer suggestions
> v4: Add test cases to test GPIO for AST2700 and update commit messages
> v5: Fix aspeed_gpio-test test failed if arch is arm
> v6: Add to test aspeed_gpio-test for aarch64
> v7: Move GPIO testcase for AST2700 to ast2700-gpio-test.c
> 
> Jamin Lin (8):
>   hw/gpio/aspeed: Fix coding style
>   hw/gpio/aspeed: Support to set the different memory size
>   hw/gpio/aspeed: Support different memory region ops
>   hw/gpio/aspeed: Fix clear incorrect interrupt status for GPIO index
>     mode
>   hw/gpio/aspeed: Add AST2700 support
>   aspeed/soc: Correct GPIO irq 130 for AST2700
>   aspeed/soc: Support GPIO for AST2700
>   tests/qtest:ast2700-gpio-test: Add GPIO test case for AST2700
> 
>  hw/arm/aspeed_ast27x0.c         |  18 +-
>  hw/gpio/aspeed_gpio.c           | 427
> ++++++++++++++++++++++++++++++--
>  include/hw/gpio/aspeed_gpio.h   |   4 +-
>  tests/qtest/ast2700-gpio-test.c |  95 +++++++
>  tests/qtest/meson.build         |   3 +
>  5 files changed, 528 insertions(+), 19 deletions(-)  create mode 100644
> tests/qtest/ast2700-gpio-test.c
> 
> --
> 2.34.1

Re: [PATCH v7 0/8] Support GPIO for AST2700
Posted by Cédric Le Goater 1 week ago
On 10/1/24 11:43, Jamin Lin wrote:
> Hi all,
> 
>> Subject: [PATCH v7 0/8] Support GPIO for AST2700
>>
> 
> I don't know why I send this patch series failed to the following email addresses and got the following errors.
> open list:All patches CC here <qemu-devel@nongnu.org>
> open list:ASPEED BMCs <qemu-arm@nongnu.org>
> 
> 2024/10/1 上午 06:43:04 - Server at nongnu.org (2001:470:142:3::10) returned '451 4.4.397 Error communicating with target host. -> 421 4.2.1 Unable to connect ->
> SocketError: Failed to connect. Winsock error code: 10051, Win32 error code: 10051'
> 
> Do you encounter the same issue?

There seem to be an issue with the mailing list. I don't know what
though.

> If no, I will re-send this patch series with Thomas reviewed tag in v8.

I think we are done with this series. I was going to apply it to
aspeed-next when I noticed b4 was not able to retrieve the patchset.
And I don't see much changes in https://patchew.org/QEMU.

So please wait a bit before resending. No hurries.

Thanks,

C.




Re: [PATCH v7 0/8] Support GPIO for AST2700
Posted by Peter Maydell 1 week ago
On Tue, 1 Oct 2024 at 12:56, Cédric Le Goater <clg@kaod.org> wrote:
>
> On 10/1/24 11:43, Jamin Lin wrote:
> > Hi all,
> >
> >> Subject: [PATCH v7 0/8] Support GPIO for AST2700
> >>
> >
> > I don't know why I send this patch series failed to the following email addresses and got the following errors.
> > open list:All patches CC here <qemu-devel@nongnu.org>
> > open list:ASPEED BMCs <qemu-arm@nongnu.org>
> >
> > 2024/10/1 上午 06:43:04 - Server at nongnu.org (2001:470:142:3::10) returned '451 4.4.397 Error communicating with target host. -> 421 4.2.1 Unable to connect ->
> > SocketError: Failed to connect. Winsock error code: 10051, Win32 error code: 10051'
> >
> > Do you encounter the same issue?
>
> There seem to be an issue with the mailing list. I don't know what
> though.

The data centre hosting the GNU servers (including the mailing
list server for nongnu.org lists) had an outage earlier, and
everything was inaccessible. It should all be back up now, I think.

thanks
-- PMM