From: "David S. Miller" <davem@redhat.com>
To: balbir_soni@hotmail.com
Cc: linux-kernel@vger.kernel.org, tigran@veritas.com
Subject: Re: KSTK_EIP and KSTK_ESP
Date: Fri, 08 Feb 2002 12:55:22 -0800 (PST) [thread overview]
Message-ID: <20020208.125522.48531421.davem@redhat.com> (raw)
In-Reply-To: <F29wLdDnNMZr4DwRMLj000174e4@hotmail.com>
In-Reply-To: <F29wLdDnNMZr4DwRMLj000174e4@hotmail.com>
From: "Balbir Singh" <balbir_soni@hotmail.com>
Date: Fri, 08 Feb 2002 12:36:59 -0800
Do we really need these defines, I found that it
is not used anywhere and defined as deadbeef on
some architectures. Does it make sense to remove
these variables from the kernel source?
Perhaps your copy of grep is buggy, check out
fs/proc/array.c which does make use of those macros.
next prev parent reply other threads:[~2002-02-08 20:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-08 20:36 Balbir Singh
2002-02-08 20:55 ` David S. Miller [this message]
2002-02-11 6:20 ` Albert D. Cahalan
2002-02-08 21:08 Balbir Singh
2004-11-05 23:13 Hanson, Jonathan M
2004-11-06 12:54 ` Arjan van de Ven
2004-11-08 17:36 Hanson, Jonathan M
2004-11-08 18:56 ` pageexec
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=20020208.125522.48531421.davem@redhat.com \
--to=davem@redhat.com \
--cc=balbir_soni@hotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tigran@veritas.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 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®