linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?b?w43DsWlnbyBIdWd1ZXQgPGlodWd1ZXRAcmVkaGF0LmNvbT4=?=@ci.codeaurora.org
Cc: rajur@chelsio.com, davem@davemloft.net, kuba@kernel.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	ivecera@redhat.com
Subject: Re: [PATCH 1/2] net:cxgb3: replace tasklets with works
Date: Thu, 03 Jun 2021 22:00:03 +0000	[thread overview]
Message-ID: <162275760359.27338.14404110046111441464.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210603063430.6613-1-ihuguet@redhat.com>

Hello:

This series was applied to netdev/net-next.git (refs/heads/master):

On Thu,  3 Jun 2021 08:34:29 +0200 you wrote:
> OFLD and CTRL TX queues can be stopped if there is no room in
> their DMA rings. If this happens, they're tried to be restarted
> later after having made some room in the corresponding ring.
> 
> The tasks of restarting these queues were triggered using
> tasklets, but they can be replaced for workqueue works, getting
> them out of softirq context.
> 
> [...]

Here is the summary with links:
  - [1/2] net:cxgb3: replace tasklets with works
    https://git.kernel.org/netdev/net-next/c/5e0b8928927f
  - [2/2] net:cxgb3: fix code style issues
    https://git.kernel.org/netdev/net-next/c/6a8dd8b2fa5b

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



      parent reply	other threads:[~2021-06-03 22:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-03  6:34 [PATCH 1/2] net:cxgb3: replace tasklets with works Íñigo Huguet
2021-06-03  6:34 ` [PATCH 2/2] net:cxgb3: fix code style issues Íñigo Huguet
     [not found] ` <20210603074419.2930-1-hdanton@sina.com>
2021-06-03 12:33   ` [PATCH 1/2] net:cxgb3: replace tasklets with works Íñigo Huguet
     [not found]     ` <20210604031450.3039-1-hdanton@sina.com>
2021-06-04 11:19       ` Íñigo Huguet
2021-06-03 22: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=162275760359.27338.14404110046111441464.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc==?utf-8?b?w43DsWlnbyBIdWd1ZXQgPGlodWd1ZXRAcmVkaGF0LmNvbT4=?=@ci.codeaurora.org \
    --cc=davem@davemloft.net \
    --cc=ivecera@redhat.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=rajur@chelsio.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;
as well as URLs for NNTP newsgroup(s).