summaryrefslogtreecommitdiff
path: root/fs/gfs2/export.c
diff options
context:
space:
mode:
authorMauro Carvalho Chehab <mchehab+huawei@kernel.org>2020-04-14 18:48:27 +0200
committerJonathan Corbet <corbet@lwn.net>2020-04-20 15:35:58 -0600
commit346282db9c6bc7ce2dad8ae640494f3f88d23889 (patch)
treeacfea8454e31fb600d618d0a7dc53dcd3e1e7eff /fs/gfs2/export.c
parent2f9c502552cd3e791db91ee80f7766e122b3b026 (diff)
downloadlwn-346282db9c6bc7ce2dad8ae640494f3f88d23889.tar.gz
lwn-346282db9c6bc7ce2dad8ae640494f3f88d23889.zip
scripts: kernel-doc: proper handle @foo->bar()
The pattern @foo->bar() is valid, as it can be used by a function pointer inside a struct passed as a parameter. Right now, it causes a warning: ./drivers/firewire/core-transaction.c:606: WARNING: Inline strong start-string without end-string. In this specific case, the kernel-doc markup is: /** * fw_core_remove_address_handler() - unregister an address handler * @handler: callback * * To be called in process context. * * When fw_core_remove_address_handler() returns, @handler->callback() is * guaranteed to not run on any CPU anymore. */ With seems valid on my eyes. So, instead of trying to hack the kernel-doc markup, let's teach it about how to handle such things. This should likely remove lots of other similar warnings as well. Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org> Link: https://lore.kernel.org/r/48b46426d7bf6ff7529f20e5718fbf4e9758e62c.1586881715.git.mchehab+huawei@kernel.org Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Diffstat (limited to 'fs/gfs2/export.c')
0 files changed, 0 insertions, 0 deletions