Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot compilation using uClibc and activating bluez
Date: Tue, 9 Jul 2013 17:14:04 +0200	[thread overview]
Message-ID: <20130709171404.1fc94ea6@skate> (raw)
In-Reply-To: <747C1E83C744F44E9ACFB89FAEEC2C7B2423BF9A50@EXDCVYMBSTM005.EQ1STM.local>

Dear Julien COUVRAND,

On Tue, 9 Jul 2013 16:36:15 +0200, Julien COUVRAND wrote:
> Thanks Thomas
> I am going to check it.

Please don't reply to me directly: keep the list Cc'ed.

Now that my network connection is working a little bit better, the
Blackfin guys indeed have a noMMU patch for D-Bus, at
http://blackfin.uclinux.org/git/?p=buildroot;a=blob;f=package/dbus/dbus-nommu.patch;h=bd1cf4c00b454634648a7d074f2f7bda009b6581;hb=HEAD.
It'd be great if you could test it, clean it up, and submit it to
Buildroot.

Just curious, which noMMU architecture are you working on?

Thanks,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  parent reply	other threads:[~2013-07-09 15:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-09  8:57 [Buildroot] Buildroot compilation using uClibc and activating bluez Julien COUVRAND
2013-07-09 10:50 ` Thomas Petazzoni
     [not found]   ` <747C1E83C744F44E9ACFB89FAEEC2C7B2423BF9A50@EXDCVYMBSTM005.EQ1STM.local>
2013-07-09 15:14     ` Thomas Petazzoni [this message]
     [not found]       ` <747C1E83C744F44E9ACFB89FAEEC2C7B2423BF9A66@EXDCVYMBSTM005.EQ1STM.local>
     [not found]         ` <20130709173907.06199659@skate>
2013-07-10  7:56           ` Julien COUVRAND
2013-07-10  9:04             ` Thomas Petazzoni
2013-07-09 10:50 ` 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=20130709171404.1fc94ea6@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