From: Aurelien Jarno <aurelien@aurel32.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qemu: Add support for suffixes to the -m parameter
Date: Fri, 11 Apr 2008 20:37:13 +0200 [thread overview]
Message-ID: <47FFAFD9.2020900@aurel32.net> (raw)
In-Reply-To: <1207935830-27938-1-git-send-email-amit.shah@qumranet.com>
Amit Shah a écrit :
> The -m parameter doesn't take suffixes like G or M currently
> and it doesn't complain if such a suffix is given.
>
> Add support for the G and M suffixes and update the usage
> instructions appropriately.
>
Such a patch as already been submitted by Anthony Liguori in the "[PATCH
1/5] Use correct types to enable > 2G support (v3)" patch.
I am currently testing it, and trying to fix the > 3.5G support. I plan
to commit it as soon this problem is fixed.
--
.''`. Aurelien Jarno | GPG: 1024D/F1BCDB73
: :' : Debian developer | Electrical Engineer
`. `' aurel32@debian.org | aurelien@aurel32.net
`- people.debian.org/~aurel32 | www.aurel32.net
prev parent reply other threads:[~2008-04-11 18:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-11 17:43 [Qemu-devel] [PATCH] qemu: Add support for suffixes to the -m parameter Amit Shah
2008-04-11 18:37 ` Aurelien Jarno [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=47FFAFD9.2020900@aurel32.net \
--to=aurelien@aurel32.net \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).