From: Sascha Hauer <s.hauer@pengutronix.de>
To: Alexander Aring <alex.aring@googlemail.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] documentation: add sandbox malloc argument
Date: Sat, 13 Oct 2012 14:30:24 +0200 [thread overview]
Message-ID: <20121013123024.GX27665@pengutronix.de> (raw)
In-Reply-To: <1350068157-601-1-git-send-email-alex.aring@gmail.com>
On Fri, Oct 12, 2012 at 08:55:57PM +0200, Alexander Aring wrote:
> Add malloc argument in doxygen comment.
>
> Signed-off-by: Alexander Aring <alex.aring@gmail.com>
Applied, thanks
Sascha
> ---
> arch/sandbox/os/common.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/arch/sandbox/os/common.c b/arch/sandbox/os/common.c
> index db347e2..36c8d62 100644
> --- a/arch/sandbox/os/common.c
> +++ b/arch/sandbox/os/common.c
> @@ -436,6 +436,10 @@ static void print_usage(const char *prgname)
> *
> * Options can be:
> *
> + * -m, --malloc=\<size\>
> + *
> + * Start sandbox with a specified malloc-space \<size\> in bytes.
> + *
> * -i \<file\>
> *
> * Map a \<file\> to barebox. This option can be given multiple times. The \<file\>s
> --
> 1.7.12.2
>
>
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox
>
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2012-10-13 12:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-12 18:55 Alexander Aring
2012-10-13 12:30 ` Sascha Hauer [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=20121013123024.GX27665@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=alex.aring@googlemail.com \
--cc=barebox@lists.infradead.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