From: Jakub Kicinski <kuba@kernel.org>
To: Pavan Chebbi <pavan.chebbi@broadcom.com>
Cc: michael.chan@broadcom.com, davem@davemloft.net,
edumazet@google.com, gospo@broadcom.com, netdev@vger.kernel.org,
pabeni@redhat.com, richardcochran@gmail.com
Subject: Re: [PATCH net-next v2 0/3] bnxt PTP optimizations
Date: Tue, 21 Mar 2023 12:24:14 -0700 [thread overview]
Message-ID: <20230321122414.5cc09af6@kernel.org> (raw)
In-Reply-To: <20230321144449.15289-1-pavan.chebbi@broadcom.com>
On Tue, 21 Mar 2023 07:44:46 -0700 Pavan Chebbi wrote:
> Patches to
> 1. Enforce software based freq adjustments only on shared PHC NIC
>
> 2. A prerequisite change to expand capability storage field to
> accommodate more Firmware reported capabilities
You reposted too soon, have read of the process doc:
https://www.kernel.org/doc/html/next/process/maintainer-netdev.html
next prev parent reply other threads:[~2023-03-21 19:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 14:44 [PATCH net-next v2 0/3] bnxt PTP optimizations Pavan Chebbi
2023-03-21 14:44 ` [PATCH net-next v2 1/3] bnxt: Change fw_cap to u64 to accommodate more capability bits Pavan Chebbi
2023-03-21 14:44 ` [PATCH net-next v2 2/3] bnxt: Defer PTP initialization to after querying function caps Pavan Chebbi
2023-03-21 14:44 ` [PATCH net-next v2 3/3] bnxt: Enforce PTP software freq adjustments only when in non-RTC mode Pavan Chebbi
2023-03-21 19:24 ` Jakub Kicinski [this message]
2023-03-22 5:54 ` [PATCH net-next v2 0/3] bnxt PTP optimizations Pavan Chebbi
2023-03-22 15:29 ` Vadim Fedorenko
2023-03-23 3:50 ` patchwork-bot+netdevbpf
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=20230321122414.5cc09af6@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gospo@broadcom.com \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavan.chebbi@broadcom.com \
--cc=richardcochran@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.