From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] uclibc: Add UCLIBC_MMU_CONFIG to UCLIBC_SETUP_DOT_CONFIG
Date: Thu, 5 Sep 2013 23:32:02 +0200 [thread overview]
Message-ID: <20130905233202.12ae0e26@skate> (raw)
In-Reply-To: <1378347859.1658.1.camel@phoenix>
Dear Axel Lin,
On Thu, 05 Sep 2013 10:24:19 +0800, Axel Lin wrote:
> commit c798bec25 "uclibc: set MMU usage accordingly" defines UCLIBC_MMU_CONFIG,
> but forgot adding it to UCLIBC_SETUP_DOT_CONFIG. Fix it.
>
> Signed-off-by: Axel Lin <axel.lin@ingics.com>
> Cc: Gustavo Zacarias <gustavo@zacarias.com.ar>
Acked-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-09-05 21:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-05 2:24 [Buildroot] [PATCH] uclibc: Add UCLIBC_MMU_CONFIG to UCLIBC_SETUP_DOT_CONFIG Axel Lin
2013-09-05 21:32 ` Thomas Petazzoni [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-09-18 7:38 Axel Lin
2013-09-18 16:38 ` Thomas Petazzoni
2013-09-18 22:30 ` Peter Korsgaard
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=20130905233202.12ae0e26@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox