From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: <linux-kernel@vger.kernel.org>
Cc: Paul Gortmaker <paul.gortmaker@windriver.com>,
Rusty Russell <rusty@rustcorp.com.au>
Subject: [PATCH] extable.h: add stddef.h so "NULL" definition is not implicit
Date: Wed, 27 Jul 2016 23:11:47 -0400 [thread overview]
Message-ID: <20160728031147.26362-1-paul.gortmaker@windriver.com> (raw)
While not an issue now, eventually we will have independent users of
the extable.h file and we will stop sourcing it via module.h header.
In testing that pending work, with very sparse builds, characteristic
of an "allnoconfig" on various architectures, we can sometimes hit an
instance where the very basic standard definitions aren't present,
resulting in:
include/linux/extable.h:26:9: error: 'NULL' undeclared (first use in this function)
To be clear, this isn't a regression, since currently extable.h is
only used by module.h -- however, we will need this addition present
before we start migrating exception table users off module.h and onto
extable.h during the next release cycle.
Cc: Rusty Russell <rusty@rustcorp.com.au>
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
---
[Was not expecting extable.h to be in 4.8 content, but since it is, it
might as well have this one line fixup to make it ready for 4.9 ; feel
free to squash this into the original extable.h creation if rebasing.]
include/linux/extable.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/include/linux/extable.h b/include/linux/extable.h
index 2c71dccd1bc3..7effea4b257d 100644
--- a/include/linux/extable.h
+++ b/include/linux/extable.h
@@ -1,6 +1,8 @@
#ifndef _LINUX_EXTABLE_H
#define _LINUX_EXTABLE_H
+#include <linux/stddef.h> /* for NULL */
+
struct module;
struct exception_table_entry;
--
2.8.4
next reply other threads:[~2016-07-28 3:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-28 3:11 Paul Gortmaker [this message]
2016-07-28 5:54 ` [PATCH] extable.h: add stddef.h so "NULL" definition is not implicit Rusty Russell
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=20160728031147.26362-1-paul.gortmaker@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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