From: Keith Owens <kaos@ocs.com.au>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] BUG() disassembly tweak
Date: Sat, 11 May 2002 13:03:00 +1000 [thread overview]
Message-ID: <4058.1021086180@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Sat, 11 May 2002 02:58:32 +0100." <Pine.LNX.4.21.0205110255410.2235-100000@localhost.localdomain>
On Sat, 11 May 2002 02:58:32 +0100 (BST),
Hugh Dickins <hugh@veritas.com> wrote:
>Is there some escaped syntax whereby we can (usefully) put
>KBUILD_BASENAME into the BUG() macro in place of __FILE__?
AFAICT without testing it, you should be able to directly replace
__FILE__ with KBUILD_BASENAME. Both are just pre-processor variables.
On my bells and whistles list (things to add after kbuild 2.5 is in the
kernel) is KBUILD_UNIQUE_NAME. That variable will contain enough of
the pathname to uniquely identify the source. For globally unique
names it is the same as KBUILD_BASENAME with a .[cS] suffix. For
repeated filenames like inode.c it is fs/inode.c for the top level,
ext2/inode.c for an individual filesystem.
next prev parent reply other threads:[~2002-05-11 3:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-10 21:22 Hugh Dickins
2002-05-10 22:10 ` Linus Torvalds
2002-05-10 22:51 ` Dave Jones
2002-05-11 11:42 ` Ingo Oeser
2002-05-10 22:58 ` Andrew Morton
2002-05-11 0:00 ` Keith Owens
2002-05-11 1:58 ` Hugh Dickins
2002-05-11 2:32 ` Kai Germaschewski
2002-05-11 3:03 ` Keith Owens [this message]
2002-05-11 1:04 ` Hugh Dickins
2002-05-11 1:34 ` Keith Owens
2002-05-11 1:39 ` Keith Owens
2002-05-11 2:07 ` Hugh Dickins
2002-05-11 2:21 ` Keith Owens
2002-05-13 15:31 ` Hugh Dickins
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=4058.1021086180@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®