All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: nic_swsd@realtek.com, pabeni@redhat.com, davem@davemloft.net,
	kuba@kernel.org, edumazet@google.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] r8169: improve handling task scheduling
Date: Thu, 30 Nov 2023 03:50:27 +0000	[thread overview]
Message-ID: <170131622723.14621.8854537531511799398.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <c65873a3-7394-4107-99a7-83f20030779c@gmail.com>

Hello:

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

On Mon, 27 Nov 2023 18:20:11 +0100 you wrote:
> If we know that the task is going to be a no-op, don't even schedule it.
> And remove the check for netif_running() in the worker function, the
> check for flag RTL_FLAG_TASK_ENABLED is sufficient. Note that we can't
> remove the check for flag RTL_FLAG_TASK_ENABLED in the worker function
> because we have no guarantee when it will be executed.
> 
> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
> 
> [...]

Here is the summary with links:
  - [net-next] r8169: improve handling task scheduling
    https://git.kernel.org/netdev/net-next/c/127532cd0f06

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



      parent reply	other threads:[~2023-11-30  3:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-27 17:20 [PATCH net-next] r8169: improve handling task scheduling Heiner Kallweit
2023-11-28 11:53 ` Przemek Kitszel
2023-11-30  3: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=170131622723.14621.8854537531511799398.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nic_swsd@realtek.com \
    --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.