From: patchwork-bot+netdevbpf@kernel.org
To: Luka Gejak <luka.gejak@linux.dev>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org, horms@kernel.org,
fmaurer@redhat.com, liuhangbin@gmail.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/2] net: hsr: subsystem cleanups and modernization
Date: Sun, 29 Mar 2026 21:40:26 +0000 [thread overview]
Message-ID: <177482042679.472023.17711197467583379324.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260326174600.136232-1-luka.gejak@linux.dev>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 26 Mar 2026 18:45:58 +0100 you wrote:
> From: Luka Gejak <luka.gejak@linux.dev>
>
> Changes in v2:
> - dropped trivial cleanup-only patches per netdev clean-up policy
> - added AI attribution for cover-letter/commit-message wording only
> - dropped fallthrough/BIT conversion patches per review
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] net: hsr: constify hsr_ops and prp_ops protocol operation structures
https://git.kernel.org/netdev/net-next/c/3e09b370f830
- [net-next,v2,2/2] net: hsr: use __func__ instead of hardcoded function name
https://git.kernel.org/netdev/net-next/c/137ac69c15fd
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:[~2026-03-29 21:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 17:45 [PATCH net-next v2 0/2] net: hsr: subsystem cleanups and modernization luka.gejak
2026-03-26 17:45 ` [PATCH net-next v2 1/2] net: hsr: constify hsr_ops and prp_ops protocol operation structures luka.gejak
2026-03-26 17:46 ` [PATCH net-next v2 2/2] net: hsr: use __func__ instead of hardcoded function name luka.gejak
2026-03-27 12:01 ` [PATCH net-next v2 0/2] net: hsr: subsystem cleanups and modernization Felix Maurer
2026-03-29 21:40 ` 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=177482042679.472023.17711197467583379324.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fmaurer@redhat.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuhangbin@gmail.com \
--cc=luka.gejak@linux.dev \
--cc=netdev@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox