All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felix Maurer <fmaurer@redhat.com>
To: luka.gejak@linux.dev
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, netdev@vger.kernel.org, horms@kernel.org,
	liuhangbin@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/2] net: hsr: subsystem cleanups and modernization
Date: Fri, 27 Mar 2026 13:01:25 +0100	[thread overview]
Message-ID: <acZxlczkaUE9dVGQ@thinkpad> (raw)
In-Reply-To: <20260326174600.136232-1-luka.gejak@linux.dev>

On Thu, Mar 26, 2026 at 06:45:58PM +0100, luka.gejak@linux.dev 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

Thank you for updating (and limiting) the series.

> This series contains two focused HSR cleanups with practical benefit.
> It constifies protocol operation tables and replaces a hardcoded
> function name with __func__ to keep diagnostics correct across
> refactoring.
> Assisted-by: Copilot:gpt-5.3-codex (cover-letter/commit-message wording
> only)
>
> Luka Gejak (2):
>   net: hsr: constify hsr_ops and prp_ops protocol operation structures
>   net: hsr: use __func__ instead of hardcoded function name

The patches look good to me, so for the series:
Reviewed-by: Felix Maurer <fmaurer@redhat.com>

Thanks,
   Felix


  parent reply	other threads:[~2026-03-27 12:01 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 ` Felix Maurer [this message]
2026-03-29 21:40 ` [PATCH net-next v2 0/2] net: hsr: subsystem cleanups and modernization patchwork-bot+netdevbpf

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=acZxlczkaUE9dVGQ@thinkpad \
    --to=fmaurer@redhat.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.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 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.