public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Shinas Rasheed <srasheed@marvell.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	hgani@marvell.com, egallen@redhat.com, mschmidt@redhat.com,
	vimleshk@marvell.com, vburru@marvell.com, sedara@marvell.com,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com
Subject: Re: [net-next PATCH] octeon_ep: support to fetch firmware info
Date: Mon, 18 Sep 2023 06:10:23 +0000	[thread overview]
Message-ID: <169501742301.10972.7267111808150683547.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230915081608.2155837-1-srasheed@marvell.com>

Hello:

This patch was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:

On Fri, 15 Sep 2023 01:16:07 -0700 you wrote:
> Add support to fetch firmware info such as heartbeat miss count,
> heartbeat interval. This shall be used for heartbeat monitor.
> 
> Signed-off-by: Shinas Rasheed <srasheed@marvell.com>
> ---
>  .../marvell/octeon_ep/octep_cn9k_pf.c         | 10 +++-----
>  .../ethernet/marvell/octeon_ep/octep_config.h | 22 +++++++++++++----
>  .../marvell/octeon_ep/octep_ctrl_net.c        | 24 ++++++++++++++++++-
>  .../marvell/octeon_ep/octep_ctrl_net.h        | 18 ++++++++++++++
>  .../ethernet/marvell/octeon_ep/octep_main.c   | 16 +++++++++----
>  .../marvell/octeon_ep/octep_regs_cn9k_pf.h    |  4 ++++
>  6 files changed, 77 insertions(+), 17 deletions(-)

Here is the summary with links:
  - [net-next] octeon_ep: support to fetch firmware info
    https://git.kernel.org/netdev/net-next/c/8d6198a14e2b

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2023-09-18  6:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-15  8:16 [net-next PATCH] octeon_ep: support to fetch firmware info Shinas Rasheed
2023-09-18  6:10 ` patchwork-bot+netdevbpf [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=169501742301.10972.7267111808150683547.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=egallen@redhat.com \
    --cc=hgani@marvell.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mschmidt@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sedara@marvell.com \
    --cc=srasheed@marvell.com \
    --cc=vburru@marvell.com \
    --cc=vimleshk@marvell.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