selinux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ondrej Mosnacek <omosnace@redhat.com>
To: selinux@vger.kernel.org, Paul Moore <paul@paul-moore.com>
Cc: Stephen Smalley <sds@tycho.nsa.gov>,
	linux-security-module@vger.kernel.org, kbuild-all@01.org,
	Ondrej Mosnacek <omosnace@redhat.com>,
	kbuild test robot <lkp@intel.com>
Subject: [PATCH] LSM: lsm_hooks.h - fix missing colon in docstring
Date: Mon, 25 Mar 2019 09:05:35 +0100	[thread overview]
Message-ID: <20190325080535.19475-1-omosnace@redhat.com> (raw)
In-Reply-To: <201903211834.Qtb0LJ32%lkp@intel.com>

Apparently without it it is incorrect syntax and causes a warning about
undocumented struct field.

Fixes: b230d5aba2d1 ("LSM: add new hook for kernfs node initialization")
Reported-by: kbuild test robot <lkp@intel.com>
Signed-off-by: Ondrej Mosnacek <omosnace@redhat.com>
---
 include/linux/lsm_hooks.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/include/linux/lsm_hooks.h b/include/linux/lsm_hooks.h
index 0dd5bda719e6..b987dc282d63 100644
--- a/include/linux/lsm_hooks.h
+++ b/include/linux/lsm_hooks.h
@@ -447,7 +447,7 @@
  *
  * Security hooks for kernfs node operations
  *
- * @kernfs_init_security
+ * @kernfs_init_security:
  *	Initialize the security context of a newly created kernfs node based
  *	on its own and its parent's attributes.
  *
-- 
2.20.1


  parent reply	other threads:[~2019-03-25  8:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-21 10:47 [pcmoore-selinux:next 8/10] htmldocs: include/linux/lsm_hooks.h:1814: warning: Function parameter or member 'kernfs_init_security' not described in 'security_list_options' kbuild test robot
2019-03-22  6:57 ` Ondrej Mosnacek
2019-03-25  8:05 ` Ondrej Mosnacek [this message]
2019-03-25 14:08   ` [PATCH] LSM: lsm_hooks.h - fix missing colon in docstring Paul Moore

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=20190325080535.19475-1-omosnace@redhat.com \
    --to=omosnace@redhat.com \
    --cc=kbuild-all@01.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=paul@paul-moore.com \
    --cc=sds@tycho.nsa.gov \
    --cc=selinux@vger.kernel.org \
    /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).