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] [PATCH] package/cairo: uses fork(), so requires an MMU
Date: Thu, 15 May 2014 10:02:51 +0200	[thread overview]
Message-ID: <20140515100251.0f503b8d@free-electrons.com> (raw)
In-Reply-To: <20140515074408.GA11475@pc-eric>

Dear Eric Le Bihan,

On Thu, 15 May 2014 09:44:08 +0200, Eric Le Bihan wrote:

> On Thu, May 15, 2014 at 12:15:37AM +0200, Yann E. MORIN wrote:
> > On 2014-05-14 23:56 +0200, Yann E. MORIN spake thusly:
> > > From: "Yann E. MORIN" <yann.morin.1998@free.fr>
> > >
> > > Fixes:
> > >     http://autobuild.buildroot.net/results/038/038371cc8548b3d39d8174289bedc9aae4076303/
> >
> > Also fixes:
> >     http://autobuild.buildroot.net/results/d93/d9374c1bd08eae5db60e6939ce5e9e4c8ff8cbd5/
> >     http://autobuild.buildroot.net/results/574/5746e7e3b2bc36f31dee1acf71e59dc4d6c90af2/
> >     http://autobuild.buildroot.net/results/b66/b66d7125ea7e10313221462097ae6c22ede963e5/
> >     [...]
> 
> A few weeks ago, I posted a fix to cairo for these issues:
> 
> http://patchwork.ozlabs.org/patch/342715/
> 
> The problem occurs on one of the test program, not on cairo itself, so cairo
> should be usable on Blackfin (I do not own one, so I have not tested it).
> 
> I opened a bug at freedesktop.org too:
> 
> https://bugs.freedesktop.org/show_bug.cgi?id=78709

Yep, I agree Eric's patch is better. I've therefore marked Yann's patch
as rejected (hope you won't mind Yann).

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2014-05-15  8:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-14 21:56 [Buildroot] [PATCH] package/cairo: uses fork(), so requires an MMU Yann E. MORIN
2014-05-14 22:15 ` Yann E. MORIN
2014-05-15  7:44   ` Eric Le Bihan
2014-05-15  8:02     ` Thomas Petazzoni [this message]
2014-05-15 16:24       ` Yann E. MORIN

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=20140515100251.0f503b8d@free-electrons.com \
    --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