From: Hugh Dickins <hugh@veritas.com>
To: Chris Wright <chrisw@sous-sol.org>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: [PATCH trivial] security: remove unused forwards
Date: Sun, 29 Jun 2008 00:55:49 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0806290054351.18327@blonde.site> (raw)
Why would linux/security.h need forward declarations for nfsctl_arg
and swap_info_struct? It's hard to imagine: remove them.
Signed-off-by: Hugh Dickins <hugh@veritas.com>
---
include/linux/security.h | 2 --
1 file changed, 2 deletions(-)
--- linux-next/include/linux/security.h 2008-06-27 13:39:19.000000000 +0100
+++ linux/include/linux/security.h 2008-06-27 14:08:00.000000000 +0100
@@ -101,9 +101,7 @@ extern unsigned long mmap_min_addr;
#define LSM_SETID_FS 8
/* forward declares to avoid warnings */
-struct nfsctl_arg;
struct sched_param;
-struct swap_info_struct;
struct request_sock;
/* bprm_apply_creds unsafe reasons */
next reply other threads:[~2008-06-28 23:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-28 23:55 Hugh Dickins [this message]
2008-06-30 10:58 ` James Morris
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=Pine.LNX.4.64.0806290054351.18327@blonde.site \
--to=hugh@veritas.com \
--cc=akpm@linux-foundation.org \
--cc=chrisw@sous-sol.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®