From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v8 7/7] package: Introduce NOMMU symbol
Date: Tue, 14 May 2013 09:30:54 +0200 [thread overview]
Message-ID: <20130514093054.0ef4e5fd@skate> (raw)
In-Reply-To: <CAJxxZ0OzT8DLQ+jmPCEE3+ybk+DmBMwtC2EXLbV9s1R_EN8Qhg@mail.gmail.com>
Dear Sonic Zhang,
On Tue, 14 May 2013 15:28:23 +0800, Sonic Zhang wrote:
> > For the 2013.05 cycle, it is now too late to get functional patches in,
> > Peter is now only taking fixes. Though we can continue the work and get
> > them merged in -next.
> >
> > Regarding this patch specifically (PATCH 7/7), I have never been happy
> > with it, because I don't like the idea of passing globally this
> > -D__NOMMU__ symbol all around, while it's not a standard symbol.
> >
> > I've asked Peter, and he agrees with this position. Therefore, what we
> > would like to see is -D__NOMMU__ added only to those packages that
> > actually need it.
>
> OK. This is fine to me.
Thanks. Of course, this is our current position. Depending on how many
packages are affected, and how things turn out to work, we may decide
otherwise in the future. But for now, we'd prefer to have it on a
per-package basis to really understand which packages are affected by
that.
> > Regarding PATCH 6/7, since the 2013.05 cycle is over for new patches, I
> > was hoping to find some time to look and it and refactor it. But I
> > believe I'll just test it once again, give my Acked-by: so it gets
> > merged, and then later on find the time to refactor it.
> >
> > Would this be ok for you?
>
> Yes, having your Acked-by for -next tree is good enough.
Ok, so I'll work on testing your patch as is.
> > Also, while we're at it, I've just launched a new version of our
> > autobuilders infrastructure (see
> > http://lists.busybox.net/pipermail/buildroot/2013-May/072143.html).
> > Would you be interested in receiving a daily e-mail that contains only
> > the list of Blackfin related build failures?
>
> I am find to receive these notify email by my gmail account.
Ok, will do so.
Thanks,
Thomas
--
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-05-14 7:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-06 7:35 [Buildroot] [PATCH v8 6/7] arch: toolchain: Install blackfin FDPIC and FLAT libraries in external toolchain makefile Sonic Zhang
2013-05-06 7:35 ` [Buildroot] [PATCH v8 7/7] package: Introduce NOMMU symbol Sonic Zhang
2013-05-14 6:23 ` Sonic Zhang
2013-05-14 7:15 ` Thomas Petazzoni
2013-05-14 7:28 ` Sonic Zhang
2013-05-14 7:30 ` Thomas Petazzoni [this message]
2013-05-14 6:22 ` [Buildroot] [PATCH v8 6/7] arch: toolchain: Install blackfin FDPIC and FLAT libraries in external toolchain makefile Sonic Zhang
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=20130514093054.0ef4e5fd@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