netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Peter Seiderer <ps.report@gmx.net>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, horms@kernel.org, toke@redhat.com
Subject: Re: [PATCH net-next v2 0/3] net: pktgen: fix checkpatch code style errors/warnings
Date: Thu, 17 Apr 2025 11:20:39 +0000	[thread overview]
Message-ID: <174488883923.4039084.4754428619480833278.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250415112916.113455-1-ps.report@gmx.net>

Hello:

This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Tue, 15 Apr 2025 13:29:13 +0200 you wrote:
> Fix checkpatch detected code style errors/warnings detected in
> the file net/core/pktgen.c (remaining checkpatch checks will be addressed
> in a follow up patch set).
> 
> Changes v1 -> v2:
>   - drop already applied patches
>   - update "net: pktgen: fix code style (ERROR: else should follow close brace
>     '}')"
>     Additional add braces around the else statement (as suggested by a follow
>     up checkpatch run and by Jakub Kicinski from code review).
>   - update "net: pktgen: fix code style (WARNING: please, no space before tabs)"
>     Change from spaces to tab for indent (suggested by Jakub Kicinski).
>   - update "net: pktgen: fix code style (WARNING: Prefer strscpy over strcpy)"
>     Squash memset/strscpy pattern into single strscpy_pad call (suggested
>     by Jakub Kicinski).
>   - drop "net: pktgen: fix code style (WARNING: braces {} are not necessary for
>     single statement blocks)" (suggestd by Jakub Kicinski)
> 
> [...]

Here is the summary with links:
  - [net-next,v2,1/3] net: pktgen: fix code style (ERROR: else should follow close brace '}')
    https://git.kernel.org/netdev/net-next/c/3bc1ca7e173c
  - [net-next,v2,2/3] net: pktgen: fix code style (WARNING: please, no space before tabs)
    https://git.kernel.org/netdev/net-next/c/65f5b9cb5431
  - [net-next,v2,3/3] net: pktgen: fix code style (WARNING: Prefer strscpy over strcpy)
    https://git.kernel.org/netdev/net-next/c/422cf22aa332

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



      parent reply	other threads:[~2025-04-17 11:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-15 11:29 [PATCH net-next v2 0/3] net: pktgen: fix checkpatch code style errors/warnings Peter Seiderer
2025-04-15 11:29 ` [PATCH net-next v2 1/3] net: pktgen: fix code style (ERROR: else should follow close brace '}') Peter Seiderer
2025-04-16 17:18   ` Simon Horman
2025-04-15 11:29 ` [PATCH net-next v2 2/3] net: pktgen: fix code style (WARNING: please, no space before tabs) Peter Seiderer
2025-04-16 17:18   ` Simon Horman
2025-04-15 11:29 ` [PATCH net-next v2 3/3] net: pktgen: fix code style (WARNING: Prefer strscpy over strcpy) Peter Seiderer
2025-04-16 17:18   ` Simon Horman
2025-04-17 11:20 ` 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=174488883923.4039084.4754428619480833278.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=ps.report@gmx.net \
    --cc=toke@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;
as well as URLs for NNTP newsgroup(s).