All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J . A . Magallon" <jamagallon@able.es>
To: Hugh Dickins <hugh@veritas.com>
Cc: Paul Gortmaker <p_gortmaker@yahoo.com>,
	Keith Owens <kaos@ocs.com.au>,
	linux-kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] a more efficient BUG() macro
Date: Sat, 17 Feb 2001 15:22:40 +0100	[thread overview]
Message-ID: <20010217152240.A2641@werewolf.able.es> (raw)
In-Reply-To: <3A8E3BA5.4B98E94E@yahoo.com> <Pine.LNX.4.21.0102171200530.2029-100000@localhost.localdomain>
In-Reply-To: <Pine.LNX.4.21.0102171200530.2029-100000@localhost.localdomain>; from hugh@veritas.com on Sat, Feb 17, 2001 at 14:15:42 +0100


On 02.17 Hugh Dickins wrote:
> On Sat, 17 Feb 2001, Paul Gortmaker wrote:
> > I was poking around in a vmlinux the other day and was surprised at the 
> > amount of repetitive crap text that was in there.  For example, try:
> > 
> > strings vmlinux|grep $PWD|wc -c
> > 

If you try
strings vmlinux|grep /usr

you get a bunch of strings like:
..
/usr/src/linux/include/asm/io.h
..

One other couple of Kb. The problem is not that, but the string comes from:
/usr/src/linux/include/asm/io.h:
..(line 110)
/*
 * Temporary debugging check to catch old code using
 * unmapped ISA addresses. Will be removed in 2.4.
 */
#if 1
  extern void *__io_virt_debug(unsigned long x, const char *file, int line);
  extern unsigned long __io_phys_debug(unsigned long x, const char *file, int li
ne);
  #define __io_virt(x) __io_virt_debug((unsigned long)(x), __FILE__, __LINE__)
//#define __io_phys(x) __io_phys_debug((unsigned long)(x), __FILE__, __LINE__)
#else
  #define __io_virt(x) ((void *)(x))
//#define __io_phys(x) __pa(x)
#endif
..

As you see, it was not removed in 2.4...

-- 
J.A. Magallon                                                      $> cd pub
mailto:jamagallon@able.es                                          $> more beer

Linux werewolf 2.4.1-ac17 #1 SMP Sat Feb 17 01:47:56 CET 2001 i686


  reply	other threads:[~2001-02-17 14:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-17  8:51 [PATCH] a more efficient BUG() macro Paul Gortmaker
2001-02-17 12:26 ` Manfred Spraul
2001-02-17 12:57   ` Pauline Middelink
2001-02-17 13:15 ` Hugh Dickins
2001-02-17 14:22   ` J . A . Magallon [this message]
2001-02-17 15:14     ` J . A . Magallon
2001-02-17 17:04       ` [PATCH] conditionalize __io_virt_debug Jeff Garzik
2001-02-18  0:01   ` [PATCH] a more efficient BUG() macro Keith Owens
2001-02-18  0:33     ` J . A . Magallon
2001-02-18  0:48       ` Keith Owens
2001-02-18  1:33         ` Andrew Morton
2001-02-18  1:37           ` J . A . Magallon
2001-02-18  1:50             ` Andrew Morton
2001-02-18  1:47           ` Keith Owens
2001-02-18 14:27     ` Andi Kleen
2001-02-17 16:37 ` J . A . Magallon

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=20010217152240.A2641@werewolf.able.es \
    --to=jamagallon@able.es \
    --cc=hugh@veritas.com \
    --cc=kaos@ocs.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=p_gortmaker@yahoo.com \
    /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.