From: Michal Marek <mmarek@suse•cz>
To: Arnaud Lacombe <lacombar@gmail•com>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: [PATCH] kconfig: fix warning
Date: Mon, 27 Dec 2010 21:53:35 +0100 [thread overview]
Message-ID: <20101227205335.GF21436@pobox.suse.cz> (raw)
In-Reply-To: <1293092716-15765-1-git-send-email-lacombar@gmail.com>
On Thu, Dec 23, 2010 at 03:25:16AM -0500, Arnaud Lacombe wrote:
> In file included from scripts/kconfig/zconf.tab.c:2502:
> scripts/kconfig/expr.c:1033: warning: no previous prototype for 'expr_simplify_unmet_dep'
>
> Reported-by: Stephen Rothwell <sfr@canb•auug.org.au>
> Signed-off-by: Arnaud Lacombe <lacombar@gmail•com>
> ---
> scripts/kconfig/expr.h | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
Applied to kbuild-2.6.git#kconfig, thanks.
Michal
>
> diff --git a/scripts/kconfig/expr.h b/scripts/kconfig/expr.h
> index 218991b..79ab6e7 100644
> --- a/scripts/kconfig/expr.h
> +++ b/scripts/kconfig/expr.h
> @@ -206,6 +206,7 @@ struct expr *expr_extract_eq_and(struct expr **ep1, struct expr **ep2);
> struct expr *expr_extract_eq_or(struct expr **ep1, struct expr **ep2);
> void expr_extract_eq(enum expr_type type, struct expr **ep, struct expr **ep1, struct expr **ep2);
> struct expr *expr_trans_compare(struct expr *e, enum expr_type type, struct symbol *sym);
> +struct expr *expr_simplify_unmet_dep(struct expr *e1, struct expr *e2);
>
> void expr_fprint(struct expr *e, FILE *out);
> struct gstr; /* forward */
> --
> 1.7.3.3
>
prev parent reply other threads:[~2010-12-27 20:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-23 0:00 linux-next: build warning after merge of the kbuild tree Stephen Rothwell
2010-12-23 8:25 ` [PATCH] kconfig: fix warning Arnaud Lacombe
2010-12-27 20:53 ` Michal Marek [this message]
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=20101227205335.GF21436@pobox.suse.cz \
--to=mmarek@suse$(echo .)cz \
--cc=lacombar@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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