mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: WangYuli <wangyuli@uniontech.com>
Cc: akpm@linux-foundation.org, guanwentao@uniontech.com,
	linux-kernel@vger.kernel.org, mingo@kernel.org,
	niecheng1@uniontech.com, tglx@linutronix.de,
	zhanjun@uniontech.com, rmody@marvell.com, skalluru@marvell.com,
	GR-Linux-NIC-Dev@marvell.com, andrew+netdev@lunn.ch,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, netdev@vger.kernel.org
Subject: Re: [PATCH v2 1/5] bna: bnad_dim_timeout: Rename del_timer_sync in comment
Date: Mon, 14 Apr 2025 22:57:35 +0000	[thread overview]
Message-ID: <174467145500.2060374.2711094592170219314.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <66962B9D4666B555+20250414042629.63019-1-wangyuli@uniontech.com>

Hello:

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

On Mon, 14 Apr 2025 12:26:25 +0800 you wrote:
> Commit 8fa7292fee5c ("treewide: Switch/rename to timer_delete[_sync]()")
> switched del_timer_sync to timer_delete_sync, but did not modify the
> comment for bnad_dim_timeout(). Now fix it.
> 
> Cc: Rasesh Mody <rmody@marvell.com>
> Cc: Sudarsana Kalluru <skalluru@marvell.com>
> Cc: GR-Linux-NIC-Dev@marvell.com
> Cc: Andrew Lunn <andrew+netdev@lunn.ch>
> Cc: David S. Miller <davem@davemloft.net>
> Cc: Eric Dumazet <edumazet@google.com>
> Cc: Jakub Kicinski <kuba@kernel.org>
> Cc: Paolo Abeni <pabeni@redhat.com>
> Cc: netdev@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org
> Signed-off-by: WangYuli <wangyuli@uniontech.com>
> 
> [...]

Here is the summary with links:
  - [v2,1/5] bna: bnad_dim_timeout: Rename del_timer_sync in comment
    https://git.kernel.org/netdev/net-next/c/1450e4525f9a
  - [v2,4/5] ipvs: ip_vs_conn_expire_now: Rename del_timer in comment
    (no matching commit)

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



  reply	other threads:[~2025-04-14 22:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-14  4:22 [PATCH v2 0/5] treewide: Rename del_timer[_sync] " WangYuli
2025-04-14  4:26 ` [PATCH v2 1/5] bna: bnad_dim_timeout: Rename del_timer_sync " WangYuli
2025-04-14 22:57   ` patchwork-bot+netdevbpf [this message]
2025-04-14  4:26 ` [PATCH v2 2/5] ocfs2: o2net_idle_timer: " WangYuli
2025-04-14  4:26 ` [PATCH v2 3/5] scsi: scsi_transport_fc: Rename del_timer " WangYuli
2025-04-22  0:54   ` Martin K. Petersen
2025-04-14  4:26 ` [PATCH v2 4/5] ipvs: ip_vs_conn_expire_now: " WangYuli
2025-04-14  4:26 ` [PATCH v2 5/5] ALSA: korg1212: snd_korg1212_prepare: " WangYuli
2025-04-14  8:34   ` Philipp Stanner
2025-04-14 11:10     ` WangYuli
2025-04-15 15:45       ` Takashi Iwai

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=174467145500.2060374.2711094592170219314.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=GR-Linux-NIC-Dev@marvell.com \
    --cc=akpm@linux-foundation.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=guanwentao@uniontech.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=niecheng1@uniontech.com \
    --cc=pabeni@redhat.com \
    --cc=rmody@marvell.com \
    --cc=skalluru@marvell.com \
    --cc=tglx@linutronix.de \
    --cc=wangyuli@uniontech.com \
    --cc=zhanjun@uniontech.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

all inboxes | Powered by JetHome®