From: Jakub Kicinski <kuba@kernel.org>
To: Edward Cree <ecree.xilinx@gmail.com>
Cc: Simon Horman <horms@kernel.org>,
edward.cree@amd.com, linux-net-drivers@amd.com,
davem@davemloft.net, pabeni@redhat.com, edumazet@google.com,
netdev@vger.kernel.org, habetsm.xilinx@gmail.com,
Jonathan Cooper <jonathan.s.cooper@amd.com>
Subject: Re: [PATCH net-next 7/7] sfc: add debugfs node for filter table contents
Date: Tue, 12 Dec 2023 08:19:44 -0800 [thread overview]
Message-ID: <20231212081944.2480f57b@kernel.org> (raw)
In-Reply-To: <b9456284-432d-2254-0af2-1dedeca0183d@gmail.com>
On Tue, 12 Dec 2023 15:14:17 +0000 Edward Cree wrote:
> On 12/12/2023 13:58, Edward Cree wrote:
> > On 11/12/2023 19:17, Simon Horman wrote:
> >> On Mon, Dec 11, 2023 at 05:18:32PM +0000, edward.cree@amd.com wrote:
> [...]
> >>
> >> Hi Edward,
> >>
> >> I think that probably the above should be static inline.
> >
> > Yep, in fact there are instances of this from patch 2 onwards (most
> > of those aren't even static). Clearly I hadn't had enough sleep
> > the day I wrote this :/
> Or maybe it's *today* I haven't had enough sleep...
> Unlike the functions in patches 2-4, which are stubs for the
> CONFIG_DEBUG_FS=n build, these functions should *not* be "static
> inline", because they are intended to be referenced from ops
> structs or passed as callbacks.
> The check on patchwork is actually a false positive here, because
> this is not a function that's defined in the header file. It's
> part of the body of a *macro*, EFX_DEBUGFS_RAW_PARAMETER.
> Functions are only defined when some C file expands the macro.
>
> I will update the commit message to call out and explain this; I
> believe the code is actually fine.
Fair point, second time in a ~month we see this sort of false positive.
I'll throw [^\\]$ at the end of the regex to try to avoid matching stuff
that's most likely a macro.
This one looks legit tho:
+void efx_debugfs_print_filter(char *s, size_t l, struct efx_filter_spec *spec) {}
next prev parent reply other threads:[~2023-12-12 16:19 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 17:18 [PATCH net-next 0/7] sfc: initial debugfs support edward.cree
2023-12-11 17:18 ` [PATCH net-next 1/7] sfc: initial debugfs implementation edward.cree
2023-12-15 0:05 ` Nelson, Shannon
2024-02-08 21:25 ` Edward Cree
2023-12-11 17:18 ` [PATCH net-next 2/7] sfc: debugfs for channels edward.cree
2023-12-12 19:54 ` kernel test robot
2023-12-11 17:18 ` [PATCH net-next 3/7] sfc: debugfs for (nic) RX queues edward.cree
2023-12-12 22:06 ` kernel test robot
2023-12-15 0:05 ` Nelson, Shannon
2025-02-14 15:51 ` Edward Cree
2025-02-14 17:39 ` Nelson, Shannon
2023-12-11 17:18 ` [PATCH net-next 4/7] sfc: debugfs for (nic) TX queues edward.cree
2023-12-13 0:15 ` kernel test robot
2023-12-11 17:18 ` [PATCH net-next 5/7] sfc: add debugfs nodes for loopback mode edward.cree
2023-12-11 17:18 ` [PATCH net-next 6/7] sfc: add debugfs entries for filter table status edward.cree
2023-12-11 19:25 ` Simon Horman
2023-12-15 0:05 ` Nelson, Shannon
2025-02-14 16:23 ` Edward Cree
2025-02-14 17:47 ` Nelson, Shannon
2023-12-11 17:18 ` [PATCH net-next 7/7] sfc: add debugfs node for filter table contents edward.cree
2023-12-11 19:17 ` Simon Horman
2023-12-12 13:58 ` Edward Cree
2023-12-12 15:14 ` Edward Cree
2023-12-12 16:19 ` Jakub Kicinski [this message]
2023-12-13 12:15 ` Edward Cree
2023-12-14 16:56 ` Simon Horman
2023-12-15 0:05 ` Nelson, Shannon
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=20231212081944.2480f57b@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=edward.cree@amd.com \
--cc=habetsm.xilinx@gmail.com \
--cc=horms@kernel.org \
--cc=jonathan.s.cooper@amd.com \
--cc=linux-net-drivers@amd.com \
--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.