From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] google-breakpad: disable on mips64
Date: Sun, 20 Jul 2014 10:28:11 +0200 [thread overview]
Message-ID: <20140720102811.0c9427d7@free-electrons.com> (raw)
In-Reply-To: <20140720034718.GA2478@tarshish>
Dear Baruch Siach,
On Sun, 20 Jul 2014 06:47:19 +0300, Baruch Siach wrote:
> On Sat, Jul 19, 2014 at 06:34:39PM +0200, Thomas Petazzoni wrote:
> > commit: http://git.buildroot.net/buildroot/commit/?id=7ef750f4a408322e23fc2aaa822e7afa14bcbbe7
> > branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/master
> >
> > Due to some mmap() related issue, google-breakpad fails to build on
> > mips64, so let's disable it for the moment. The mips/mips64 folks
> > might be interested in fixing that later.
> >
> > Fixes:
> >
> > http://autobuild.buildroot.org/results/2b0/2b03937693ea400ddcc7e8364ff7dc22ce651669/
> >
> > Cc: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
> > Cc: Markos Chandras <Markos.Chandras@imgtec.com>
>
> Interesting. As this patch never appeared on the list before, does the git
> commits mail sending script actually Cc these addresses?
No, it was a mistake from my side: I did had these Cc: lines as I was
planning on sending the mail to the list (to get Vicente and Markos
informed of the issue), and then only apply the patch. Unfortunately,
in the mean time, I applied other patches and I pushed everything.
Let's Cc them now :-)
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-07-20 8:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-19 16:34 [Buildroot] [git commit] google-breakpad: disable on mips64 Thomas Petazzoni
2014-07-20 3:47 ` Baruch Siach
2014-07-20 8:28 ` Thomas Petazzoni [this message]
2014-07-21 8:26 ` Markos Chandras
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=20140720102811.0c9427d7@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.