All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: linux-os@analogic.com
Cc: Pawe?? Sikora <pluto@pld-linux.org>,
	Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: [2.6 patch] kill IN_STRING_C
Date: Mon, 8 Nov 2004 23:29:52 +0100	[thread overview]
Message-ID: <20041108222952.GJ15077@stusta.de> (raw)
In-Reply-To: <Pine.LNX.4.61.0411081640320.8258@chaos.analogic.com>

On Mon, Nov 08, 2004 at 05:15:14PM -0500, linux-os wrote:
> >...
> >Are you using exactly my example file?
> >Are you using the complete gcc command line as shown by "make V=1"?
> >Which gcc 3.3.3 are you using?
> >
> 
> No, I am using (no headers):
> -------------------
> extern int sprintf(char *, const char *,...);
> extern int puts(const char *);
> static const char hello[]="Hello";
> int xxx(void);
> int xxx(){
>    char buf[0x100];
>    sprintf(buf, "%s", hello);
>    puts(buf);
>    return 0;
> }
> --------------------
> 
> Compiled as:
> 
> gcc -O2 -Wall -S -o xxx xxx.c
>...

If you don't compile the code as it would be compiled inside the kernel, 
that's your fault...

Please reply only if you can reproduce this with
#include <linux/string.h>, #include <linux/kernel.h> _and_ a gcc command
line as it would be in the kernel - everything else is useless.

> Cheers,
> Dick Johnson

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2004-11-08 22:30 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-07 14:24 [2.6 patch] kill IN_STRING_C Adrian Bunk
2004-11-08 13:44 ` Andi Kleen
2004-11-08 15:34   ` Adrian Bunk
2004-11-08 16:19     ` Andi Kleen
2004-11-08 16:31       ` Adrian Bunk
2004-11-08 17:51         ` Andi Kleen
2004-11-08 18:34           ` Adrian Bunk
2004-11-08 19:01             ` Andi Kleen
2004-11-08 23:38               ` Use -ffreestanding? Adrian Bunk
2004-11-09  5:01                 ` Andi Kleen
2004-11-10  1:45                   ` [2.6 patch] " Adrian Bunk
2004-11-10  1:51                     ` Linus Torvalds
2004-11-10  1:57                       ` Adrian Bunk
2004-11-10 21:01                       ` Bill Davidsen
2004-11-08 18:04         ` [2.6 patch] kill IN_STRING_C Paweł Sikora
2004-11-08 18:31           ` Adrian Bunk
2004-11-08 19:12             ` linux-os
2004-11-08 21:27               ` Adrian Bunk
2004-11-08 22:15                 ` linux-os
2004-11-08 22:29                   ` Adrian Bunk [this message]
2004-11-08 22:57                     ` linux-os
2004-11-08 23:08                       ` Adrian Bunk
2004-11-09 12:44                         ` linux-os
2004-11-09 13:43                           ` linux-os
2004-11-08 18:22       ` linux-os
2004-11-08 19:31         ` Ryan Cumming
2004-11-09 13:58     ` Arnd Bergmann
2004-11-10  2:30       ` Adrian Bunk
     [not found] ` <200411081942.38954.pluto@pld-linux.org>
     [not found]   ` <20041108185222.GE15077@stusta.de>
2004-11-08 19:11     ` Paweł Sikora
2004-11-08 21:25       ` Adrian Bunk
  -- strict thread matches above, loose matches on Subject: below --
2004-11-08 18:43 Paweł Sikora

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=20041108222952.GJ15077@stusta.de \
    --to=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-os@analogic.com \
    --cc=pluto@pld-linux.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.