mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Paulo Marques <pmarques@grupopie.com>
Cc: Segher Boessenkool <segher@kernel.crashing.org>,
	Mike Frysinger <vapier@gentoo.org>,
	Satyam Sharma <satyam.sharma@gmail.com>,
	Andrew Morton <akpm@osdl.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] remove usage of memmem from scripts/kallsyms.c
Date: Wed, 20 Jun 2007 18:42:55 +0200	[thread overview]
Message-ID: <20070620164255.GA11519@uranus.ravnborg.org> (raw)
In-Reply-To: <46794D6B.9050301@grupopie.com>

On Wed, Jun 20, 2007 at 04:53:15PM +0100, Paulo Marques wrote:
> Segher Boessenkool wrote:
> >>>>So we could remove the "#define _GNU_SOURCE" at the top
> >>>>of scripts/kallsyms.c too, presumably? If not (i.e. if there are
> >>>>more GNUisms left in that file anyway), then I'm not sure if we
> >>>>really gain by the change.
> >>>yes, i believe this is true
> >>
> >>I only tried in on x86 with my toolchain and it works, but I don't 
> >>know if it is worth the risk of breaking someone's setup for virtually 
> >>no gain...
> >
> >With the memmem() removed, the code builds (and works)
> >fine on several non-GNU systems.  It should be perfectly
> >safe to remove the _GNU_SOURCE. 
> 
> You're right. I went back in history and it was me who introduced the 
> _GNU_SOURCE when I added the memmem too (shame on me). So, if it worked 
> fine before, there is no reason to not work now that memmem is removed.
> 
> So I can:
> 
>  - send an incremental patch with just that line removed
> 
>  - send a replacement patch
> 
>  - just leave it for now and wait until I work on kallsyms again to 
> silently remove that line together with other changes
> 
> Andrew, what would you prefer?
Please send a replacement patch to me.
I will carry it in the kbuild tree.

	Sam

  reply	other threads:[~2007-06-20 16:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-19 16:15 Paulo Marques
2007-06-19 17:43 ` Mike Frysinger
2007-06-19 18:47 ` Satyam Sharma
2007-06-20  4:33   ` Mike Frysinger
2007-06-20 11:56     ` Paulo Marques
2007-06-20 15:25       ` Segher Boessenkool
2007-06-20 15:53         ` Paulo Marques
2007-06-20 16:42           ` Sam Ravnborg [this message]
2007-06-19 19:04 ` Christoph Hellwig
2007-06-20 11:53   ` Paulo Marques

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=20070620164255.GA11519@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmarques@grupopie.com \
    --cc=satyam.sharma@gmail.com \
    --cc=segher@kernel.crashing.org \
    --cc=vapier@gentoo.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

Powered by JetHome