All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Eric Paris <eparis@redhat.com>
Cc: malware-list@lists.printk.net, linux-kernel@vger.kernel.org
Subject: Re: request for comment: generic kernel interface for malware vendors
Date: Mon, 28 Jul 2008 20:39:44 -0700	[thread overview]
Message-ID: <20080729033944.GD12085@kroah.com> (raw)
In-Reply-To: <1216613887.2960.18.camel@localhost.localdomain>

On Mon, Jul 21, 2008 at 12:18:07AM -0400, Eric Paris wrote:
> 
> This is a request for comment.  This is a first stab and I'm here to
> address all of the concerns that people have.  Please don't hold back,
> I've got thick skin.  BUT, I don't want to hear 'this is how we have
> been doing it, do it that way.'  I want to hear how this won't work for
> your needs (and WHY) or how we can do it better.
> 
> you can find the patches at:
> http://people.redhat.com/~eparis/talpa

You need to actually send the code to the mailing list if you expect
anyone to read it :)

And we need to know what you are trying to achieve here, without that,
there is no way to evaluate if the implementation matches this or not.

thanks,

greg k-h

  parent reply	other threads:[~2008-07-29  3:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-21  4:18 request for comment: generic kernel interface for malware vendors Eric Paris
2008-07-21 11:17 ` James Morris
2008-07-24  9:58   ` Christoph Hellwig
2008-07-21 17:43 ` Rafael C. de Almeida
2008-07-21 18:14 ` Christian Borntraeger
2008-07-22  0:23   ` Eric Paris
2008-07-23 16:09 ` Ray Lee
2008-07-29  3:39 ` Greg KH [this message]
2008-07-29  4:50   ` [malware-list] " Jon Masters
2008-07-30 11:13     ` tvrtko.ursulin
2008-08-04 19:37       ` Greg KH
     [not found] <aRVce-Em-3@gated-at.bofh.it>
     [not found] ` <aS7Go-7AK-3@gated-at.bofh.it>
2008-07-23 12:43   ` Bodo Eggert
2008-07-23 15:14     ` Arjan van de Ven

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=20080729033944.GD12085@kroah.com \
    --to=greg@kroah.com \
    --cc=eparis@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=malware-list@lists.printk.net \
    /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.