From: Vladimir Kondratiev <vladimir.kondratiev@intel.com>
To: linux-kernel@vger.kernel.org
Subject: __FUNCTION__ - continue
Date: Fri, 11 Jan 2002 19:11:44 +0200 [thread overview]
Message-ID: <3C3F1CD0.2030202@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 737 bytes --]
Hello,
I am continue looking at __FUNCTION__ use in context where it
concatenates with another string. This time I attached little patch that
just fixes /include subtree. This patch do not change format of messages
printed, it just uses __FUNCTION__ as gcc 3 suggests.
Patch is against 2.4.18-pre3
All /include subtree is fixed, except /include/asm-mips/system.h (it
requires small changes in /arch/mips/kernel/traps.c)
I will come with separate fix for it, it's easy to do, I just wonder
whether this issue is interesting and patches going to be used.
Otherwise, I don't want to spend time for this technical and not very
interesting work.
P.S. Marcelo, if you are reading it - your opinion, is this issue worth
the effort?
[-- Attachment #2: __FUNCTION__.include.patch.gz --]
[-- Type: application/x-gzip, Size: 1033 bytes --]
reply other threads:[~2002-01-11 17:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3C3F1CD0.2030202@intel.com \
--to=vladimir.kondratiev@intel.com \
--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