From: patchwork-bot+netdevbpf@kernel.org
To: Justin Lai <justinlai0215@realtek.com>
Cc: kuba@kernel.org, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, andrew+netdev@lunn.ch,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
horms@kernel.org, pkshih@realtek.com, larry.chiu@realtek.com
Subject: Re: [PATCH net-next 0/2] Modifying format and renaming goto labels
Date: Sat, 16 Nov 2024 02:00:36 +0000 [thread overview]
Message-ID: <173172243608.2797219.7333896071358961263.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241114112549.376101-1-justinlai0215@realtek.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 14 Nov 2024 19:25:47 +0800 you wrote:
> This patch set primarily involves modifying the enum rtase_registers
> format and renaming the goto labels in rtase_init_one.
>
> Justin Lai (2):
> rtase: Modify the name of the goto label
> rtase: Modify the content format of the enum rtase_registers
>
> [...]
Here is the summary with links:
- [net-next,1/2] rtase: Modify the name of the goto label
https://git.kernel.org/netdev/net-next/c/fdb53791195c
- [net-next,2/2] rtase: Modify the content format of the enum rtase_registers
https://git.kernel.org/netdev/net-next/c/39007e1c1c7c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-11-16 2:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-14 11:25 [PATCH net-next 0/2] Modifying format and renaming goto labels Justin Lai
2024-11-14 11:25 ` [PATCH net-next 1/2] rtase: Modify the name of the goto label Justin Lai
2024-11-14 18:15 ` Simon Horman
2024-11-14 11:25 ` [PATCH net-next 2/2] rtase: Modify the content format of the enum rtase_registers Justin Lai
2024-11-14 18:15 ` Simon Horman
2024-11-16 2: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=173172243608.2797219.7333896071358961263.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=justinlai0215@realtek.com \
--cc=kuba@kernel.org \
--cc=larry.chiu@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pkshih@realtek.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.