mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: nktgrg <nktgrg@google.com>
Cc: netdev@vger.kernel.org, jeroendb@google.com,
	pkaligineedi@google.com, shailend@google.com,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, jfraker@google.com,
	linux-kernel@vger.kernel.org, stable@kernel.org
Subject: Re: [PATCH net-next] gve: Modify rx_buf_alloc_fail counter centrally and closer to failure
Date: Fri, 26 Jan 2024 01:20:26 +0000	[thread overview]
Message-ID: <170623202697.2360.15676490828216158973.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240124205435.1021490-1-nktgrg@google.com>

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Wed, 24 Jan 2024 20:54:35 +0000 you wrote:
> From: Ankit Garg <nktgrg@google.com>
> 
> Previously, each caller of gve_rx_alloc_buffer had to increase counter
>  and as a result one caller was not tracking those failure. Increasing
>  counters at a common location now so callers don't have to duplicate
>  code or miss counter management.
> 
> [...]

Here is the summary with links:
  - [net-next] gve: Modify rx_buf_alloc_fail counter centrally and closer to failure
    https://git.kernel.org/netdev/net-next/c/3df18416267b

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



      reply	other threads:[~2024-01-26  1:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-24 20:54 nktgrg
2024-01-26  1:20 ` 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=170623202697.2360.15676490828216158973.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=jeroendb@google.com \
    --cc=jfraker@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nktgrg@google.com \
    --cc=pabeni@redhat.com \
    --cc=pkaligineedi@google.com \
    --cc=shailend@google.com \
    --cc=stable@kernel.org \
    /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®