All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: Chris Mason <mason@suse.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, J Sloan <jjs@toyota.com>,
	Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: [lkml]Re: VM problems still in 2.2.18
Date: Sat, 16 Dec 2000 14:39:10 +0100	[thread overview]
Message-ID: <20001216143910.A25150@inspiron.random> (raw)
In-Reply-To: <E146zsJ-0001fT-00@the-village.bc.nu> <Pine.LNX.4.10.10012160244200.30931-100000@home.suse.com>
In-Reply-To: <Pine.LNX.4.10.10012160244200.30931-100000@home.suse.com>; from mason@suse.com on Sat, Dec 16, 2000 at 02:49:40AM -0800

On Sat, Dec 16, 2000 at 02:49:40AM -0800, Chris Mason wrote:
> GFP_BUFFER.  As far as I know that should be safe, but the change is

Yes that's ok.

Andrea
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-12-16 14:10 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-14  2:36 VM problems still in 2.2.18 Mark Symonds
2000-12-14  9:57 ` Alan Cox
2000-12-14 20:09   ` [lkml]Re: " thunder7
2000-12-14 22:38     ` Alan Cox
2000-12-14 22:39       ` J Sloan
2000-12-14 23:17         ` Alan Cox
2000-12-15 14:29           ` Andrea Arcangeli
2000-12-15 17:57             ` Alan Cox
2000-12-15 18:22               ` Andrea Arcangeli
2000-12-15 18:46                 ` Alan Cox
2000-12-15 19:09                   ` Andrea Arcangeli
2000-12-15 19:17                     ` Alan Cox
2000-12-16 10:49                   ` Chris Mason
2000-12-16 13:39                     ` Andrea Arcangeli [this message]
2000-12-14 23:12       ` J . A . Magallon
2000-12-18  1:03       ` Mark Symonds
2000-12-15 18:30   ` Mark Symonds
  -- strict thread matches above, loose matches on Subject: below --
2000-12-15 13:00 [lkml]Re: " Ed Tomlinson
2000-12-15 17:52 ` Alan Cox

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=20001216143910.A25150@inspiron.random \
    --to=andrea@suse.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jjs@toyota.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mason@suse.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.