All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Haiyue Wang <haiyue.wang@intel.com>
Cc: netdev@vger.kernel.org, jeroendb@google.com, csully@google.com,
	awogbemila@google.com, davem@davemloft.net, kuba@kernel.org,
	bcf@google.com, willemb@google.com, shailend@google.com,
	yangchun@google.com, sagis@google.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] gve: fix the wrong AdminQ buffer queue index check
Date: Fri, 28 Jan 2022 15:10:11 +0000	[thread overview]
Message-ID: <164338261153.2420.3816050464539840623.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220128104716.9020-1-haiyue.wang@intel.com>

Hello:

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

On Fri, 28 Jan 2022 18:47:14 +0800 you wrote:
> The 'tail' and 'head' are 'unsigned int' type free-running count, when
> 'head' is overflow, the 'int i (= tail) < u32 head' will be false:
> 
> Only '- loop 0: idx = 63' result is shown, so it needs to use 'int' type
> to compare, it can handle the overflow correctly.
> 
> typedef uint32_t u32;
> 
> [...]

Here is the summary with links:
  - [v2] gve: fix the wrong AdminQ buffer queue index check
    https://git.kernel.org/netdev/net/c/1f84a9450d75

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



      reply	other threads:[~2022-01-28 15:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-28  7:38 [PATCH v1] gve: fix the wrong AdminQ buffer queue index check Haiyue Wang
2022-01-28 10:47 ` [PATCH v2] " Haiyue Wang
2022-01-28 15: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=164338261153.2420.3816050464539840623.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=awogbemila@google.com \
    --cc=bcf@google.com \
    --cc=csully@google.com \
    --cc=davem@davemloft.net \
    --cc=haiyue.wang@intel.com \
    --cc=jeroendb@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sagis@google.com \
    --cc=shailend@google.com \
    --cc=willemb@google.com \
    --cc=yangchun@google.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.