public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Karim Yaghmour <karim@opersys.com>
To: karim@opersys.com
Cc: Andrew Morton <akpm@osdl.org>,
	Peter Martuccelli <peterm@redhat.com>,
	faith@redhat.com, davidm@hpl.hp.com, linux-ia64@vger.kernel.org,
	linux-kernel@vger.kernel.org, ray.lanza@hp.com
Subject: Re: [PATCH] IA64 audit support
Date: Thu, 01 Jul 2004 20:48:09 -0400	[thread overview]
Message-ID: <40E4B0C9.4020407@opersys.com> (raw)
In-Reply-To: <40E4B0A3.3080706@opersys.com>


Sorry, sent before completion ... will send full mail shortly.

Karim Yaghmour wrote:
> 
> Andrew Morton wrote:
> 
>> It's nice and simple.
> 
> 
> Andrew, I have got to ask:
> 
> I, and quite a few other folks, have been trying to get the Linux Trace 
> Toolkit
> in the kernel for the past 5 years and the code being added is almost 
> identical to what the audit patch adds, yet
> we've
> 
> Karim

-- 
Author, Speaker, Developer, Consultant
Pushing Embedded and Real-Time Linux Systems Beyond the Limits
http://www.opersys.com || karim@opersys.com || 1-866-677-4546


  reply	other threads:[~2004-07-02  1:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-30 15:56 [PATCH] IA64 audit support Peter Martuccelli
2004-07-01 19:46 ` Andrew Morton
2004-07-02  0:47   ` Karim Yaghmour
2004-07-02  0:48     ` Karim Yaghmour [this message]
2004-07-02  0:53   ` Karim Yaghmour
2004-07-02  1:29     ` Andrew Morton
2004-07-02  3:21       ` Karim Yaghmour
2004-07-02  6:18         ` Andrew Morton
2004-07-02 23:23           ` LTT kernel inclusion (was Re: [PATCH] IA64 audit support) Karim Yaghmour
2004-07-05 11:01           ` [PATCH] IA64 audit support Roman Zippel
2004-07-06 21:49 ` David Mosberger
  -- strict thread matches above, loose matches on Subject: below --
2004-07-01 18:01 Peter Martuccelli
2004-07-09 21:00 Peter Martuccelli

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=40E4B0C9.4020407@opersys.com \
    --to=karim@opersys.com \
    --cc=akpm@osdl.org \
    --cc=davidm@hpl.hp.com \
    --cc=faith@redhat.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterm@redhat.com \
    --cc=ray.lanza@hp.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