From: "Jan Beulich" <JBeulich@novell.com>
To: <adaplas@gmail.com>, <ilya.yanok@gmail.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: commit 68e5e9d734503695915734e50e9427624cf8f3b2 (Re: vfb: make virtual framebuffer mmapable)
Date: Fri, 02 Oct 2009 11:19:17 +0100 [thread overview]
Message-ID: <4AC5EFC50200007800017ABC@vpn.id2.novell.com> (raw)
Is there any particular reason why this change uses vmalloc_32()
rather than simply vmalloc()? I can't see why the underlying physical
address width would matter here in any way...
Thanks, Jan
next reply other threads:[~2009-10-02 10:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-02 10:19 Jan Beulich [this message]
2009-10-02 12:44 ` Ilya Yanok
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=4AC5EFC50200007800017ABC@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=adaplas@gmail.com \
--cc=ilya.yanok@gmail.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®