All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: Justin Mattock <justinmattock@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 1/1] unifdef.c change "getline" to "get_line" to avoid C library confusion.
Date: Thu, 5 Mar 2009 07:04:37 +0100	[thread overview]
Message-ID: <20090305060436.GA5359@nowhere> (raw)
In-Reply-To: <dd18b0c30903042141k1adc0f6cj4bc286cfa29f475c@mail.gmail.com>

On Wed, Mar 04, 2009 at 09:41:09PM -0800, Justin Mattock wrote:
> From: Justin P. Mattock <justinmattock@gmail.com>
> 
> This fixes an error when compiling the kernel.
> 
>   CHK     include/linux/version.h
>   HOSTCC  scripts/unifdef
> scripts/unifdef.c:209: error: conflicting types for 'getline'
> /usr/include/stdio.h:651: note: previous declaration of 'getline' was here
> make[1]: *** [scripts/unifdef] Error 1
> make: *** [__headers] Error 2
> 
> --
> scripts/unifdef.c  |  3 +++
> 1 files changed, 3 insertions(+),0 deletions(-)
> 
> diff --git a/scripts/unifdef.c b/scripts/unifdef.c
> ---a/scripts/unifdef.c
> +++b/scripts/unifdef.c
> @@ -203,1 +203,0 @@ static void             addsym(bool, bool, char *);
> 
> 
> static void             done(void);
> static void             error(const char *);
> static int              findsym(const char *);
> static void             flushline(bool);
> -static Linetype         getline(void);
> +static Linetype         get_line(void);
> static Linetype         ifeval(const char **);
> static void             ignoreoff(void);
> static void             ignoreon(void);
> static void             keywordedit(const char *);
> 
> 
> 
> 
> @@ -509,1 +509,0 @@ process(void)
> 
> 
> {
> 	Linetype lineval;
> 
> 	for (;;) {
> 		linenum++;
> -               lineval = getline();
> +		lineval = get_line();
> 		trans_table[ifstate[depth]][lineval]();
> 		debug("process %s -> %s depth %d",
> 		    linetype_name[lineval],
> 		    ifstate_name[ifstate[depth]], depth);
> 	}
> }
> 
> 
> @@ -528,1 +528,0 @@ static Linetype
> -getline(void)
> +get_line(void)
> {
> 	const char *cp;
> 
> --
> 
> 
> keep in mind I've never created a patch before,
> (so go easy on me);


Hi,

You forgot to put your Signed-off-by: Justin P. Mattock <justinmattock@gmail.com>
:)

See Documentation/SubmittingPatches

I don't know who is the maintainer of this file.
Adding Andrew in Cc.


> regards;
> 
> -- 
> Justin P. Mattock
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/


  reply	other threads:[~2009-03-05  6:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-05  5:41 [PATCH 1/1] unifdef.c change "getline" to "get_line" to avoid C library confusion Justin Mattock
2009-03-05  6:04 ` Frederic Weisbecker [this message]
2009-03-05  7:51   ` Justin Mattock
2009-03-05  8:46     ` Justin Mattock
2009-03-05  8:49       ` Justin Mattock
2009-03-05  8:57         ` Américo Wang
2009-03-05 15:33         ` Randy Dunlap
2009-03-05 17:42           ` Justin Mattock
2009-03-05  9:00       ` Frederic Weisbecker
2009-03-05 14:48         ` Justin Mattock

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=20090305060436.GA5359@nowhere \
    --to=fweisbec@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=justinmattock@gmail.com \
    --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.