public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@osdl.org>
To: "Serge E. Hallyn" <serue@us.ibm.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Chris Wright <chrisw@osdl.org>,
	Stephen Smalley <sds@epoch.ncsc.mil>,
	Christoph Hellwig <hch@infradead.org>,
	Hugh Dickins <hugh@veritas.com>, Andrew Morton <akpm@osdl.org>
Subject: Re: [RFC] [PATCH] merge *_vm_enough_memory()s into a common helper
Date: Wed, 5 Jan 2005 11:24:46 -0800	[thread overview]
Message-ID: <20050105112446.X2357@build.pdx.osdl.net> (raw)
In-Reply-To: <20050105163046.GA2060@IBM-BWN8ZTBWA01.austin.ibm.com>; from serue@us.ibm.com on Wed, Jan 05, 2005 at 10:30:46AM -0600

* Serge E. Hallyn (serue@us.ibm.com) wrote:
> Attached is a new version of the patch introducing the __vm_enough_memory
> helper, which takes into account yesterday's suggestions.  The selinux/hooks.c
> typo was definately a dangerous bug, and __vm_enough_memory() has been moved
> to vm_enough_memory()'s original location in mm/mmap.c.

Looks alright.

> Signed-off-by: Serge Hallyn <serue@us.ibm.com>

Signed-off-by: Chris Wright <chrisw@osdl.org>

thanks,
-chris
-- 
Linux Security Modules     http://lsm.immunix.org     http://lsm.bkbits.net

      reply	other threads:[~2005-01-05 19:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-04 21:48 [RFC] [PATCH] merge *_vm_enough_memory()s into a common helper Serge E. Hallyn
2005-01-04 22:10 ` Stephen Smalley
2005-01-04 22:17 ` Chris Wright
2005-01-04 22:17   ` Stephen Smalley
2005-01-04 22:26     ` Chris Wright
2005-01-04 22:59 ` Nikita Danilov
2005-01-05  0:15   ` Alan Cox
2005-01-05 11:25 ` Christoph Hellwig
2005-01-05 13:17   ` Hugh Dickins
2005-01-05 16:30 ` Serge E. Hallyn
2005-01-05 19:24   ` Chris Wright [this message]

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=20050105112446.X2357@build.pdx.osdl.net \
    --to=chrisw@osdl.org \
    --cc=akpm@osdl.org \
    --cc=hch@infradead.org \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sds@epoch.ncsc.mil \
    --cc=serue@us.ibm.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