linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: linux-sparse@vger.kernel.org
Cc: Christopher Li <sparse@chrisli.org>,
	Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Subject: [PATCH] add missing #include "char.h" to char.c
Date: Wed,  2 Nov 2016 18:15:44 +0100	[thread overview]
Message-ID: <20161102171544.17783-1-luc.vanoostenryck@gmail.com> (raw)

And so quiets a warning from sparse about undeclared
symbols when running on its own code.

Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
---
 char.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/char.c b/char.c
index 9bd3fc0d..e3f6a006 100644
--- a/char.c
+++ b/char.c
@@ -4,6 +4,7 @@
 #include "allocate.h"
 #include "token.h"
 #include "expression.h"
+#include "char.h"
 
 static const char *parse_escape(const char *p, unsigned *val, const char *end, int bits, struct position pos)
 {
-- 
2.10.1


             reply	other threads:[~2016-11-02 17:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-02 17:15 Luc Van Oostenryck [this message]
2016-11-17  8:28 ` [PATCH] add missing #include "char.h" to char.c Christopher Li

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=20161102171544.17783-1-luc.vanoostenryck@gmail.com \
    --to=luc.vanoostenryck@gmail.com \
    --cc=linux-sparse@vger.kernel.org \
    --cc=sparse@chrisli.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;
as well as URLs for NNTP newsgroup(s).