All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Moore <paul@paul-moore.com>
To: selinux@vger.kernel.org
Subject: [PATCH 08/15] selinux: fix style issues in security/selinux/include/netif.h
Date: Thu, 21 Dec 2023 17:18:51 -0500	[thread overview]
Message-ID: <20231221222342.334026-25-paul@paul-moore.com> (raw)
In-Reply-To: <20231221222342.334026-17-paul@paul-moore.com>

As part of on ongoing effort to perform more automated testing and
provide more tools for individual developers to validate their
patches before submitting, we are trying to make our code
"clang-format clean".  My hope is that once we have fixed all of our
style "quirks", developers will be able to run clang-format on their
patches to help avoid silly formatting problems and ensure their
changes fit in well with the rest of the SELinux kernel code.

Signed-off-by: Paul Moore <paul@paul-moore.com>
---
 security/selinux/include/netif.h | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/security/selinux/include/netif.h b/security/selinux/include/netif.h
index 85ec30d11144..2838bdc170dd 100644
--- a/security/selinux/include/netif.h
+++ b/security/selinux/include/netif.h
@@ -11,6 +11,7 @@
  * Copyright (C) 2007 Hewlett-Packard Development Company, L.P.
  *                    Paul Moore <paul@paul-moore.com>
  */
+
 #ifndef _SELINUX_NETIF_H_
 #define _SELINUX_NETIF_H_
 
@@ -20,5 +21,4 @@ void sel_netif_flush(void);
 
 int sel_netif_sid(struct net *ns, int ifindex, u32 *sid);
 
-#endif	/* _SELINUX_NETIF_H_ */
-
+#endif /* _SELINUX_NETIF_H_ */
-- 
2.43.0


  parent reply	other threads:[~2023-12-21 22:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-21 22:18 SELinux style fixes Paul Moore
2023-12-21 22:18 ` [PATCH 01/15] selinux: fix style issues in security/selinux/include/audit.h Paul Moore
2023-12-22 23:09   ` [PATCH 1/15] " Paul Moore
2023-12-21 22:18 ` [PATCH 02/15] selinux: fix style issues in security/selinux/include/avc.h Paul Moore
2023-12-21 22:18 ` [PATCH 03/15] selinux: align avc_has_perm_noaudit() prototype with definition Paul Moore
2023-12-21 22:18 ` [PATCH 04/15] selinux: fix style issues in security/selinux/include/avc_ss.h Paul Moore
2023-12-21 22:18 ` [PATCH 05/15] selinux: fix style issues in security/selinux/include/classmap.h Paul Moore
2023-12-21 22:18 ` [PATCH 06/15] selinux: fix style issues in security/selinux/include/conditional.h Paul Moore
2023-12-21 22:18 ` [PATCH 07/15] selinux: fix style issues in security/selinux/include/ima.h Paul Moore
2023-12-21 22:18 ` Paul Moore [this message]
2023-12-21 22:18 ` [PATCH 09/15] selinux: fix style issues with security/selinux/include/netlabel.h Paul Moore
2023-12-21 22:18 ` [PATCH 10/15] selinux: fix style issues in security/selinux/include/objsec.h Paul Moore
2023-12-21 22:18 ` [PATCH 11/15] selinux: fix style issues in security/selinux/include/policycap.h Paul Moore
2023-12-21 22:18 ` [PATCH 12/15] selinux: fix style issues with security/selinux/include/policycap_names.h Paul Moore
2023-12-21 22:18 ` [PATCH 13/15] selinux: fix style issues in security/selinux/include/security.h Paul Moore
2023-12-21 22:18 ` [PATCH 14/15] selinux: fix style issues in security/selinux/include/xfrm.h Paul Moore
2023-12-21 22:18 ` [PATCH 15/15] selinux: fix style issues in security/selinux/include/initial_sid_to_string.h 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=20231221222342.334026-25-paul@paul-moore.com \
    --to=paul@paul-moore.com \
    --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 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.