All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Sunil Goutham <sgoutham@marvell.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
	smadarf@marvell.com
Subject: Re: [net-next PATCH] octeontx2-af: Add additional register check to rvu_poll_reg()
Date: Wed, 01 Sep 2021 10:50:06 +0000	[thread overview]
Message-ID: <163049340625.3899.18268706137182004228.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1630474739-25470-1-git-send-email-sgoutham@marvell.com>

Hello:

This patch was applied to netdev/net.git (refs/heads/master):

On Wed, 1 Sep 2021 11:08:59 +0530 you wrote:
> From: Smadar Fuks <smadarf@marvell.com>
> 
> Check one more time before exiting the API with an error.
> Fix API to poll at least twice, in case there are other high priority
> tasks and this API doesn't get CPU cycles for multiple jiffies update.
> 
> In addition, increase timeout from usecs_to_jiffies(10000) to
> usecs_to_jiffies(20000), to prevent the case that for CONFIG_100HZ
> timeout will be a single jiffies.
> A single jiffies results actual timeout that can be any time between
> 1usec and 10msec. To solve this, a value of usecs_to_jiffies(20000)
> ensures that timeout is 2 jiffies.
> 
> [...]

Here is the summary with links:
  - [net-next] octeontx2-af: Add additional register check to rvu_poll_reg()
    https://git.kernel.org/netdev/net/c/21274aa17819

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



      reply	other threads:[~2021-09-01 10:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-01  5:38 [net-next PATCH] octeontx2-af: Add additional register check to rvu_poll_reg() Sunil Goutham
2021-09-01 10:50 ` 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=163049340625.3899.18268706137182004228.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sgoutham@marvell.com \
    --cc=smadarf@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 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.