From: Dragan Stancevic <visitor@xalien.org>
To: Greg KH <greg@kroah.com>
Cc: linux-security-module@wirex.com, linux-kernel@vger.kernel.org
Subject: Re: [RFC] LSM fix for stupid "empty" functions
Date: Tue, 3 Dec 2002 07:14:08 -0800 [thread overview]
Message-ID: <200212030714.08456.visitor@xalien.org> (raw)
In-Reply-To: <20021203160141.GA20844@kroah.com>
On Tuesday 03 December 2002 08:01, Greg KH wrote:
> On Mon, Dec 02, 2002 at 06:37:52PM -0800, Dragan Stancevic wrote:
> > not that I am trying to be a PITA but where did you get the information
> > that initialized variables live in .bss?
>
> I was incorrect, as was pointed out to me about 15 minutes after sending
> that email :)
Oh sorry, I didn't catch that, 13000 emails unread.
--
Peace can only come as a natural consequence
of universal enlightenment. -Dr. Nikola Tesla
next prev parent reply other threads:[~2002-12-03 15:09 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-01 8:30 [RFC] LSM fix for stupid "empty" functions Greg KH
2002-12-01 8:17 ` Crispin Cowan
2002-12-01 17:49 ` Greg KH
2002-12-01 16:59 ` Olaf Dietsche
2002-12-01 18:12 ` Greg KH
2002-12-01 17:21 ` Christoph Hellwig
2002-12-01 18:26 ` Greg KH
2002-12-03 2:37 ` Dragan Stancevic
2002-12-03 16:01 ` Greg KH
2002-12-03 15:14 ` Dragan Stancevic [this message]
2002-12-01 17:46 ` James Morris
2002-12-01 18:46 ` Olaf Dietsche
2002-12-01 20:05 ` Greg KH
2002-12-01 19:25 ` Greg KH
2002-12-02 2:00 ` James Morris
2002-12-02 6:57 ` Greg KH
2002-12-03 8:04 ` James Morris
2002-12-04 0:13 ` [RFC] LSM fix for stupid "empty" functions - take 2 Greg KH
2002-12-04 8:14 ` Chris Wright
2002-12-04 23:00 ` Greg KH
2002-12-04 23:44 ` Chris Wright
2002-12-05 0:09 ` James Morris
-- strict thread matches above, loose matches on Subject: below --
2002-12-01 18:57 [RFC] LSM fix for stupid "empty" functions Adam J. Richter
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=200212030714.08456.visitor@xalien.org \
--to=visitor@xalien.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@wirex.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.