From: Rik van Riel <riel@conectiva.com.br>
To: Matthew Wilcox <willy@debian.org>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Andrew Morton <akpm@zip.com.au>,
linux-mm@kvack.org
Subject: [PATCH] expand_stack upward growing stack & comments
Date: Tue, 6 Aug 2002 18:20:32 -0300 (BRT) [thread overview]
Message-ID: <Pine.LNX.4.44L.0208061818350.23404-100000@imladris.surriel.com> (raw)
Hi,
the following patch implements:
- expand_stack for upward growing stacks, thanks to Matthew Wilcox
- trivial: cache file->f_dentry->d_inode; saves a few bytes of compiled
size. (also by Matthew Wilcox)
- fix the comment in expand_stack that left Matthew puzzled (me)
Please apply for the next kernel,
thank you,
Rik
--
Bravely reimplemented by the knights who say "NIH".
http://www.surriel.com/ http://distro.conectiva.com/
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next reply other threads:[~2002-08-06 21:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-06 21:20 Rik van Riel [this message]
2002-08-06 21:27 ` [PATCH][PATCH] " Rik van Riel
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=Pine.LNX.4.44L.0208061818350.23404-100000@imladris.surriel.com \
--to=riel@conectiva.com.br \
--cc=akpm@zip.com.au \
--cc=linux-mm@kvack.org \
--cc=torvalds@transmeta.com \
--cc=willy@debian.org \
/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