public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Fan Gong <gongfan1@huawei.com>
Cc: zhuyikai1@h-partners.com, netdev@vger.kernel.org,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, horms@kernel.org, andrew+netdev@lunn.ch,
	linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
	luosifu@huawei.com, guoxin09@huawei.com, zhoushuai28@huawei.com,
	wulike1@huawei.com, shijing34@huawei.com,
	luoyang82@h-partners.com
Subject: Re: [PATCH net-next v03 0/4] net: hinic3: Fix code styles
Date: Fri, 30 Jan 2026 03:00:12 +0000	[thread overview]
Message-ID: <176974201260.3152167.11856090096391309419.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1769656467.git.zhuyikai1@h-partners.com>

Hello:

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

On Thu, 29 Jan 2026 12:01:07 +0800 you wrote:
> This patchset provides 4 code styles fixes:
> 
> Remove empty lines between error handling.
> Remove defensive txq_num check.
> Use array_size instead of multiplying.
> SQ use SQ_CTXT_PREF_CI_HI to improve readability.
> 
> [...]

Here is the summary with links:
  - [net-next,v03,1/4] hinic3: Fix code Style(remove empty lines between error handling)
    https://git.kernel.org/netdev/net-next/c/738ff2d2f502
  - [net-next,v03,2/4] hinic3: Remove defensive txq_num check
    https://git.kernel.org/netdev/net-next/c/34bef6a4960f
  - [net-next,v03,3/4] hinic3: Use array_size instead of multiplying
    https://git.kernel.org/netdev/net-next/c/afb81efc971e
  - [net-next,v03,4/4] hinic3: RQ use RQ_CTXT_PREF_CI_HI instead of SQ_CTXT_PREF_CI_HI
    https://git.kernel.org/netdev/net-next/c/2da903d0a84a

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



      parent reply	other threads:[~2026-01-30  3:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-29  4:01 [PATCH net-next v03 0/4] net: hinic3: Fix code styles Fan Gong
2026-01-29  4:01 ` [PATCH net-next v03 1/4] hinic3: Fix code Style(remove empty lines between error handling) Fan Gong
2026-01-29 20:12   ` Joe Damato
2026-01-29  4:01 ` [PATCH net-next v03 2/4] hinic3: Remove defensive txq_num check Fan Gong
2026-01-29  4:01 ` [PATCH net-next v03 3/4] hinic3: Use array_size instead of multiplying Fan Gong
2026-01-29 20:06   ` Joe Damato
2026-01-29  4:01 ` [PATCH net-next v03 4/4] hinic3: RQ use RQ_CTXT_PREF_CI_HI instead of SQ_CTXT_PREF_CI_HI Fan Gong
2026-01-30  3: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=176974201260.3152167.11856090096391309419.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=gongfan1@huawei.com \
    --cc=guoxin09@huawei.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luosifu@huawei.com \
    --cc=luoyang82@h-partners.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=shijing34@huawei.com \
    --cc=wulike1@huawei.com \
    --cc=zhoushuai28@huawei.com \
    --cc=zhuyikai1@h-partners.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