From: Jakub Kicinski <kuba@kernel.org>
To: Shyam Sundar S K <Shyam-sundar.S-k@amd.com>
Cc: Raju Rangoju <Raju.Rangoju@amd.com>,
netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, Tom Lendacky <thomas.lendacky@amd.com>
Subject: Re: [PATCH net 0/2] amd-xgbe: PFC and KR-Training fixes
Date: Thu, 12 Jan 2023 14:36:19 -0800 [thread overview]
Message-ID: <20230112143619.5f7e7ed0@kernel.org> (raw)
In-Reply-To: <822b51ba-3012-6084-b4eb-39e21f2c066a@amd.com>
On Thu, 12 Jan 2023 11:19:34 +0530 Shyam Sundar S K wrote:
> 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.
For Fixes of code that someone authored it'd be better if the person
is CCed, as long as their email address still works. For net-next
material, if you're posting as a co-maintainer not CCing other
maintainers is no big deal.
> But would you mind pulling this series for now? Or would you like to see
> the MAINTAINERS file getting updated first?
Yes, no need to repost this one. Just something to keep in mind for
the future.
next prev parent reply other threads:[~2023-01-12 22:36 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 [this message]
2023-01-13 4:32 ` Shyam Sundar S K
2023-01-13 19:39 ` Jakub Kicinski
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=20230112143619.5f7e7ed0@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 \
--cc=thomas.lendacky@amd.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).