netdev - Re: [PATCH net 0/2] amd-xgbe: PFC and KR-Training fixes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <822b51ba-3012-6084-b4eb-39e21f2c066a@amd.com>
Date:   Thu, 12 Jan 2023 11:19:34 +0530
From:   Shyam Sundar S K <Shyam-sundar.S-k@....com>
To:     Jakub Kicinski <kuba@...nel.org>,
        Raju Rangoju <Raju.Rangoju@....com>
Cc:     netdev@...r.kernel.org, davem@...emloft.net, edumazet@...gle.com,
        pabeni@...hat.com, Tom Lendacky <thomas.lendacky@....com>
Subject: Re: [PATCH net 0/2] amd-xgbe: PFC and KR-Training fixes



On 1/12/2023 11:12 AM, Jakub Kicinski wrote:
> On Wed, 11 Jan 2023 22:58:50 +0530 Raju Rangoju wrote:
>> 0001 - There is difference in the TX Flow Control registers (TFCR)
>> between the revisions of the hardware. Update the driver to use the
>> TFCR based on the reported version of the hardware.
>>
>> 0002 - AN restart triggered during KR training not only aborts the KR
>> training process but also move the HW to unstable state. Add the
>> necessary changes to fix kr-taining.
> 
> Please err on the side of CCing people. Here the patches under Fixes
> have Tom's sign off which makes our automation complain that he's not
> CCed. No tag from him either.
> 

I have put an Ack tag to the patches in the series, being the additional
maintainer for this driver. As Tom is busy working on other areas, I
shall be a single maintainer for this driver going forward.

I can submit a patch for the change to the MAINTAINERS file.

But would you mind pulling this series for now? Or would you like to see
the MAINTAINERS file getting updated first?

Thanks,
Shyam