From: patchwork-bot+netdevbpf@kernel.org
To: Rakesh Babu Saladi <rsaladi2@marvell.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, sgoutham@marvell.com,
gakula@marvell.com, sbhatta@marvell.com, hkelam@marvell.com
Subject: Re: [net PATCH v3 0/3] RVU Debugfs fix updates.
Date: Thu, 28 Oct 2021 14:00:08 +0000 [thread overview]
Message-ID: <163542960862.12929.13276854563783815449.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211027173234.23559-1-rsaladi2@marvell.com>
Hello:
This series was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Wed, 27 Oct 2021 23:02:31 +0530 you wrote:
> The following patch series consists of the patch fixes done over
> rvu_debugfs.c and rvu_nix.c files.
>
> Patch 1: Check and return if ipolicers do not exists.
> Patch 2: Fix rsrc_alloc to print all enabled PF/VF entries with list of LFs
> allocated for each functional block.
> Patch 3: Fix possible null pointer dereference.
>
> [...]
Here is the summary with links:
- [net,v3,1/3] octeontx2-af: Check whether ipolicers exists
https://git.kernel.org/netdev/net/c/cc45b96e2de7
- [net,v3,2/3] octeontx2-af: Display all enabled PF VF rsrc_alloc entries.
https://git.kernel.org/netdev/net/c/e77bcdd1f639
- [net,v3,3/3] octeontx2-af: Fix possible null pointer dereference.
https://git.kernel.org/netdev/net/c/c2d4c543f74c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-10-28 14:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-27 17:32 Rakesh Babu Saladi
2021-10-27 17:32 ` [net PATCH v3 1/3] octeontx2-af: Check whether ipolicers exists Rakesh Babu Saladi
2021-10-27 17:32 ` [net PATCH v3 2/3] octeontx2-af: Display all enabled PF VF rsrc_alloc entries Rakesh Babu Saladi
2021-10-27 17:32 ` [net PATCH v3 3/3] octeontx2-af: Fix possible null pointer dereference Rakesh Babu Saladi
2021-10-28 14:00 ` 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=163542960862.12929.13276854563783815449.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rsaladi2@marvell.com \
--cc=sbhatta@marvell.com \
--cc=sgoutham@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
all inboxes | Powered by JetHome®