From: Alexey Dobriyan <adobriyan@gmail.com>
To: akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] proc: use #pragma once
Date: Tue, 24 Apr 2018 00:35:34 +0300 [thread overview]
Message-ID: <20180423213534.GA9043@avx2> (raw)
Bring /proc into 21st century.
Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
---
fs/proc/fd.h | 6 +-----
fs/proc/internal.h | 1 +
include/linux/proc_fs.h | 6 +-----
3 files changed, 3 insertions(+), 10 deletions(-)
--- a/fs/proc/fd.h
+++ b/fs/proc/fd.h
@@ -1,7 +1,5 @@
/* SPDX-License-Identifier: GPL-2.0 */
-#ifndef __PROCFS_FD_H__
-#define __PROCFS_FD_H__
-
+#pragma once
#include <linux/fs.h>
extern const struct file_operations proc_fd_operations;
@@ -16,5 +14,3 @@ static inline unsigned int proc_fd(struct inode *inode)
{
return PROC_I(inode)->fd;
}
-
-#endif /* __PROCFS_FD_H__ */
--- a/fs/proc/internal.h
+++ b/fs/proc/internal.h
@@ -1,3 +1,4 @@
+#pragma once
/* Internal procfs definitions
*
* Copyright (C) 2004 Red Hat, Inc. All Rights Reserved.
--- a/include/linux/proc_fs.h
+++ b/include/linux/proc_fs.h
@@ -1,10 +1,8 @@
/* SPDX-License-Identifier: GPL-2.0 */
+#pragma once
/*
* The proc filesystem constants/structures
*/
-#ifndef _LINUX_PROC_FS_H
-#define _LINUX_PROC_FS_H
-
#include <linux/types.h>
#include <linux/fs.h>
@@ -82,5 +80,3 @@ static inline struct proc_dir_entry *proc_net_mkdir(
struct ns_common;
int open_related_ns(struct ns_common *ns,
struct ns_common *(*get_ns)(struct ns_common *ns));
-
-#endif /* _LINUX_PROC_FS_H */
next reply other threads:[~2018-04-23 21:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-23 21:35 Alexey Dobriyan [this message]
2018-04-24 13:54 ` [PATCH] proc: use #pragma once Christoph Hellwig
2018-04-25 20:55 ` Alexey Dobriyan
2018-04-26 10:26 ` David Sterba
2018-04-26 10:33 ` Christoph Hellwig
2018-04-26 19:25 ` Alexey Dobriyan
2018-04-26 19:24 ` Alexey Dobriyan
2018-05-01 22:13 ` Andrew Morton
2018-05-03 22:14 ` Rasmus Villemoes
2018-05-03 22:42 ` Al Viro
2018-05-03 23:23 ` Rasmus Villemoes
2018-05-04 2:58 ` Al Viro
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=20180423213534.GA9043@avx2 \
--to=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@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.