public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paulo Marques <pmarques@grupopie.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kbuild <linux-kbuild@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Keith Owens <kaos@ocs.com.au>
Subject: Re: [RFC PATCH] drop support for KALLSYMS_EXTRA_PASS
Date: Wed, 04 Jun 2008 15:01:51 +0100	[thread overview]
Message-ID: <4846A04F.1030909@grupopie.com> (raw)
In-Reply-To: <20080603210732.GA6247@uranus.ravnborg.org>

Sam Ravnborg wrote:
> We have not seen any reports on inconsistent kallsysms data recently
> as in the last one or two years. At least I do not recall these
> and google had no hits in my searching.
> 
> So I suggest removing this as to simplify the final linking.
> When doing "make allyesconfig" build this extra linking
> takes considerably time (and I usually forgoet to turn it off).

I don't remember any recent (read: in the last few years) problems 
either, so I guess this is ok.

> In addition this patch removes the debug target: debug_kallsyms

This might be useful if changes in some binutils version creates new 
problems for kallsyms, but it doesn't seem like a lot of work to just 
send a reporter a patch to add this back if needed. Since there haven't 
been any reports in a few years, I have no problems with this.

Acked-by: Paulo Marques <pmarques@grupopie.com>

-- 
Paulo Marques - www.grupopie.com

"'thinking outside the box' works better if I know what's inside the box."

  reply	other threads:[~2008-06-04 14:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-03 21:07 [RFC PATCH] drop support for KALLSYMS_EXTRA_PASS Sam Ravnborg
2008-06-04 14:01 ` Paulo Marques [this message]
2008-06-05  9:19 ` Keith Owens
2008-06-07 10:51   ` Sam Ravnborg

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=4846A04F.1030909@grupopie.com \
    --to=pmarques@grupopie.com \
    --cc=kaos@ocs.com.au \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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