Netdev List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
	pabeni@redhat.com, amritha.nambiar@intel.com, jiri@resnulli.us,
	donald.hunter@gmail.com, chuck.lever@oracle.com, sdf@google.com
Subject: Re: [PATCH net-next] tools: ynl-gen: change spacing around __attribute__
Date: Mon, 23 Oct 2023 17:20:23 +0000	[thread overview]
Message-ID: <169808162349.28677.5756404188521560663.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231020221827.3436697-1-kuba@kernel.org>

Hello:

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

On Fri, 20 Oct 2023 15:18:27 -0700 you wrote:
> checkpatch gets confused and treats __attribute__ as a function call.
> It complains about white space before "(":
> 
> WARNING:SPACING: space prohibited between function name and open parenthesis '('
> +	struct netdev_queue_get_rsp obj __attribute__ ((aligned (8)));
> 
> No spaces wins in the kernel:
> 
> [...]

Here is the summary with links:
  - [net-next] tools: ynl-gen: change spacing around __attribute__
    https://git.kernel.org/netdev/net-next/c/c0119e62b2fe

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



      parent reply	other threads:[~2023-10-23 17:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-20 22:18 [PATCH net-next] tools: ynl-gen: change spacing around __attribute__ Jakub Kicinski
2023-10-20 22:26 ` Stanislav Fomichev
2023-10-21  0:32 ` Nambiar, Amritha
2023-10-21 11:23 ` Jiri Pirko
2023-10-23 17: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=169808162349.28677.5756404188521560663.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=amritha.nambiar@intel.com \
    --cc=chuck.lever@oracle.com \
    --cc=davem@davemloft.net \
    --cc=donald.hunter@gmail.com \
    --cc=edumazet@google.com \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sdf@google.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