From: Simon Horman <horms@kernel.org>
To: "zhengping.zhang" <aquapinn@qq.com>
Cc: lorenzo@kernel.org, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, upstream@airoha.com,
zhengping.zhang@airoha.com
Subject: Re: [PATCH] net: airoha: fix typo in function name
Date: Fri, 13 Feb 2026 15:26:54 +0000 [thread overview]
Message-ID: <aY9Cvud7rSw_aWU1@horms.kernel.org> (raw)
In-Reply-To: <tencent_5F3DFF496EC95F5BC0D71C297D088B06F40A@qq.com>
On Fri, Feb 13, 2026 at 02:57:25PM +0800, zhengping.zhang wrote:
> Corrected the typo in the function name from `airhoa_is_lan_gdm_port`
> to `airoha_is_lan_gdm_port`.
> This change ensures consistency in the API naming convention.
>
> Signed-off-by: zhengping.zhang <aquapinn@qq.com>
Hi,
I agree that this change is both correct and complete.
So please feel free to add:
Reviewed-by: Simon Horman <horms@kernel.org>
This looks like net-next to me material as it isn't a bug fix.
And it's best to include the target tree in the subject, like this.
Subject: [PATCH net-next] ...
Unfortunately net-next is closed at this time.
---
## Form letter - net-next-closed
We have already submitted our pull request with net-next material for v7.0,
and therefore net-next is closed for new drivers, features, code refactoring
and optimizations. We are currently accepting bug fixes only.
Please repost when net-next reopens after Feb 23rd.
RFC patches sent for review only are obviously welcome at any time.
See: https://www.kernel.org/doc/html/next/process/maintainer-netdev.html#development-cycle
--
pw-bot: defer
prev parent reply other threads:[~2026-02-13 15:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-13 6:57 [PATCH] net: airoha: fix typo in function name zhengping.zhang
2026-02-13 15:26 ` Simon Horman [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=aY9Cvud7rSw_aWU1@horms.kernel.org \
--to=horms@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=aquapinn@qq.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=lorenzo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=upstream@airoha.com \
--cc=zhengping.zhang@airoha.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.