netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Raju Rangoju <Raju.Rangoju@amd.com>
Cc: <netdev@vger.kernel.org>, <davem@davemloft.net>,
	<edumazet@google.com>, <pabeni@redhat.com>,
	<Shyam-sundar.S-k@amd.com>
Subject: Re: [PATCH net 0/2] amd-xgbe: PFC and KR-Training fixes
Date: Fri, 13 Jan 2023 11:39:31 -0800	[thread overview]
Message-ID: <20230113113931.6d70d025@kernel.org> (raw)
In-Reply-To: <20230111172852.1875384-1-Raju.Rangoju@amd.com>

On Wed, 11 Jan 2023 22:58:50 +0530 Raju Rangoju wrote:
> This patch series fixes the issues in kr-training and pfc
> 
> Patches:
> 
> 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.

Applied, thanks!

      parent reply	other threads:[~2023-01-13 19:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-11 17:28 [PATCH net 0/2] amd-xgbe: PFC and KR-Training fixes Raju Rangoju
2023-01-11 17:28 ` [PATCH net 1/2] amd-xgbe: TX Flow Ctrl Registers are h/w ver dependent Raju Rangoju
2023-01-11 17:28 ` [PATCH net 2/2] amd-xgbe: Delay AN timeout during KR training Raju Rangoju
2023-01-12  5:42 ` [PATCH net 0/2] amd-xgbe: PFC and KR-Training fixes Jakub Kicinski
2023-01-12  5:49   ` Shyam Sundar S K
2023-01-12 22:36     ` Jakub Kicinski
2023-01-13  4:32       ` Shyam Sundar S K
2023-01-13 19:39 ` Jakub Kicinski [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230113113931.6d70d025@kernel.org \
    --to=kuba@kernel.org \
    --cc=Raju.Rangoju@amd.com \
    --cc=Shyam-sundar.S-k@amd.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).