From: Jeff Dike <jdike@addtoit.com>
To: Oleg Drokin <green@linuxhacker.ru>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] export ket_kmem_end()
Date: Thu, 18 Dec 2003 16:18:42 -0500 [thread overview]
Message-ID: <20031218211842.GB3705@ccure.user-mode-linux.org> (raw)
In-Reply-To: <20031212163816.GA10993@linuxhacker.ru>
On Fri, Dec 12, 2003 at 06:38:17PM +0200, Oleg Drokin wrote:
> The functions get_kmem_end() should be exported which patch below
> does.
Applied, thanks.
Jeff
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
prev parent reply other threads:[~2003-12-18 21:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-12 16:38 [uml-devel] export ket_kmem_end() Oleg Drokin
2003-12-18 21:18 ` Jeff Dike [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=20031218211842.GB3705@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=green@linuxhacker.ru \
--cc=user-mode-linux-devel@lists.sourceforge.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.