All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Horatiu Vultur <horatiu.vultur@microchip.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, UNGLinuxDriver@microchip.com
Subject: Re: [PATCH net-next] net: lan966x: Add VCAP debugFS support
Date: Fri, 03 Feb 2023 09:40:21 +0000	[thread overview]
Message-ID: <167541722100.18212.15632360857861253388.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230202145337.234086-1-horatiu.vultur@microchip.com>

Hello:

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

On Thu, 2 Feb 2023 15:53:37 +0100 you wrote:
> Enable debugfs for vcap for lan966x. This will allow to print all the
> entries in the VCAP and also the port information regarding which keys
> are configured.
> 
> Signed-off-by: Horatiu Vultur <horatiu.vultur@microchip.com>
> ---
>  .../net/ethernet/microchip/lan966x/Makefile   |  2 +
>  .../ethernet/microchip/lan966x/lan966x_main.c |  4 +
>  .../ethernet/microchip/lan966x/lan966x_main.h | 26 +++++
>  .../microchip/lan966x/lan966x_vcap_debugfs.c  | 94 +++++++++++++++++++
>  .../microchip/lan966x/lan966x_vcap_impl.c     | 26 ++---
>  5 files changed, 136 insertions(+), 16 deletions(-)
>  create mode 100644 drivers/net/ethernet/microchip/lan966x/lan966x_vcap_debugfs.c

Here is the summary with links:
  - [net-next] net: lan966x: Add VCAP debugFS support
    https://git.kernel.org/netdev/net-next/c/942814840127

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



      reply	other threads:[~2023-02-03  9:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-02 14:53 [PATCH net-next] net: lan966x: Add VCAP debugFS support Horatiu Vultur
2023-02-03  9:40 ` 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=167541722100.18212.15632360857861253388.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horatiu.vultur@microchip.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.