From: Rakib Mullick <rakib.mullick@gmail.com>
To: Michal Marek <mmarek@suse.cz>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kbuild@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [PATCH] kconfig: Add missing prototype
Date: Wed, 18 Nov 2009 16:52:48 +0600 [thread overview]
Message-ID: <b9df5fa10911180252l577deb1bm6d8aab76b912aad5@mail.gmail.com> (raw)
In-Reply-To: <4B03CA6E.8080102@suse.cz>
On 11/18/09, Michal Marek <mmarek@suse.cz> wrote:
>
> Hi Rakib,
>
> thanks for the fix, but I already posted a new, simplified version that
> doesn't use the fprintf2() thing at all:
> http://patchwork.kernel.org/patch/50131/
>
Hi Michal,
Sorry I couldn't pick that up. Maybe it's not in the current -mm tree.
Isn't it? Does your simplified version removes the use of fprintf2()?
Thanks,
Rakib
>
> Michal
>
>
>
> > When building defconfig on i386 - we were hit by the following warning:
> >
> > HOSTCC scripts/kconfig/zconf.tab.o
> > In file included from scripts/kconfig/zconf.tab.c:2451:
> > scripts/kconfig/confdata.c:676: warning: no previous prototype for 'fprintf2'
> >
> > Signed-off-by: Rakib Mullick <rakib.mullick@gmail.com>
> > ---
> >
> > --- linus/scripts/kconfig/lkc.h 2009-11-18 16:37:46.000000000 +0600
> > +++ rakib/scripts/kconfig/lkc.h 2009-11-18 17:03:19.000000000 +0600
> > @@ -79,6 +79,7 @@ char *conf_get_default_confname(void);
> > void sym_set_change_count(int count);
> > void sym_add_change_count(int count);
> > void conf_set_all_new_symbols(enum conf_def_mode mode);
> > +int fprintf2(FILE *f1, FILE *f2, const char *fmt, ...);
> >
> > /* kconfig_load.c */
> > void kconfig_load(void);
>
>
next prev parent reply other threads:[~2009-11-18 10:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-18 10:12 [PATCH] kconfig: Add missing prototype Rakib Mullick
2009-11-18 10:20 ` Michal Marek
2009-11-18 10:52 ` Rakib Mullick [this message]
2009-11-19 7:35 ` Michal Marek
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=b9df5fa10911180252l577deb1bm6d8aab76b912aad5@mail.gmail.com \
--to=rakib.mullick@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=sam@ravnborg.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