mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Dale Farnsworth" <dale@farnsworth.org>
To: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Still no ramfs usage limits in 2.5.9 or 2.4.19-pre8
Date: Thu, 16 May 2002 09:49:26 -0700	[thread overview]
Message-ID: <20020516164926.GA16670@farnsworth.org> (raw)

David Gibson produced a patch about 18 months ago that added usage limits
to ramfs.  <http://ozlabs.org/people/dgibson/dwg-ramfs.patch>

Through 2.4.10, the AC kernel series carried this patch.

Linus' kernel from 2.4.11 onward adopted only one line from the
patch, the following attribution comment:
	"Usage limits added by David Gibson, Linuxcare Australia."

The usage limit code is missing, however.

Was this a simple mistake that has been overlooked?  Or are there
drawbacks to applying the patch that keep it out of the mainstream
kernels?

-Dale Farnsworth

             reply	other threads:[~2002-05-16 16:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-16 16:49 Dale Farnsworth [this message]
2002-05-16 18:11 ` Alan Cox
2002-05-17 11:01 ` Padraig Brady
2002-05-17 12:18   ` 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=20020516164926.GA16670@farnsworth.org \
    --to=dale@farnsworth.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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

all inboxes | Powered by JetHome®