From: Gideon Israel Dsouza <gidisrael@gmail.com>
To: paul@paul-moore.com, sds@tycho.nsa.gov, eparis@parisplace.org,
akpm@linux-foundation.org
Cc: geert@linux-m68k.org, linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org,
Gideon Israel Dsouza <gidisrael@gmail.com>
Subject: [PATCH] security: Use macros from compiler.h instead of gcc specific attributes
Date: Wed, 11 Jun 2014 21:25:29 +0530 [thread overview]
Message-ID: <1402502130-26400-1-git-send-email-gidisrael@gmail.com> (raw)
NOTE: Please ignore the earlier similar emails. I apologize sincerely
for the mistake.
To increase compiler portability there is <linux/compiler.h> which
provides convenience macros for various gcc constructs. Eg: __weak for
__attribute__((weak)).
I've taken up the job of cleaning these attributes all over the kernel.
Currently my patches for cleanup of all files under /kernel, /block and
/mm are already done and in the linux 3.15 tree.
In the following patch I've replaced all aforementioned instances under
the /security directory in the kernel source.
Gideon Israel Dsouza (1):
security: Used macros from compiler.h instead of __attribute__((...))
security/selinux/include/security.h | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
--
1.9.3
next reply other threads:[~2014-06-11 15:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-11 15:55 Gideon Israel Dsouza [this message]
2014-06-11 15:55 ` [PATCH 1/1] security: Used macros from compiler.h instead of __attribute__((...)) Gideon Israel Dsouza
2014-06-18 18:50 ` Paul Moore
2014-06-18 20:08 ` Geert Uytterhoeven
2014-06-18 20:58 ` Paul Moore
2014-06-26 11:45 ` Gideon D'souza
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=1402502130-26400-1-git-send-email-gidisrael@gmail.com \
--to=gidisrael@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=eparis@parisplace.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=sds@tycho.nsa.gov \
/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®