From: Emil Velikov <emil.l.velikov@gmail.com>
To: "Gore, Tim" <tim.gore@intel.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Cc: emil.l.velikov@gmail.com
Subject: Re: [PATCHv2 0/8] Upstreaming the Android build and misc fixes
Date: Fri, 29 Aug 2014 11:02:53 +0100 [thread overview]
Message-ID: <54004FCD.8060701@gmail.com> (raw)
In-Reply-To: <8FCC70911F3E9548866CA0E51893BCC31A201CE2@IRSMSX105.ger.corp.intel.com>
Hi Tim,
On 29/08/14 10:44, Gore, Tim wrote:
> Hi Emil, sorry for the delay.
> I still see the same patch error for patch 3/8. The patch diff
> for intel/makefile.am has as part of its context:
>
> # Eric Anholt <eric at anholt.net>
>
> Whereas the source file has
>
> # Eric Anholt <eric@anholt.net>
>
> So the patch fails. Its trivial of course. Perhaps there is some automatic
> Substitution getting done by some tool.
The issue you're seeing here is (afaik) an anti-spam feature. The ML
software/parser automatically substitutes/obscures email addresses.
For any future case, I would recommend adding a remote branch rather than
picking patches from mailling-lists - not all of them play nice :\
> Maybe git-am will automatically
> Fix this, not sure, I don't have a workflow for git-am.
> My source comes from
> Git://anongit.freedesktop.org/git/mesa/drm
> Remote =origin
> Merge = refs/heads/master
>
> Other than that, as I say the patches look fine, and I have successfully built
> Libdrm in an Android tree using these patches and "mm".
> I am out of the office from 12:00 until Thurs 4th Sept now.
>
Nice. They build fine on my end as well. I've even had a couple of people test
them (with a mmap patch on top) alongside mesa 10.2 :)
I was hoping for an acked-by/reviewed-by, but it seems like I'll push the
series as is.
Thanks
Emil
> Tim
>
prev parent reply other threads:[~2014-08-29 10:03 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-27 18:25 [PATCH 0/8] Upstreaming the Android build and misc fixes Emil Velikov
2014-07-27 18:25 ` [PATCH 1/8] all: include config.h only when available and use its defines Emil Velikov
2014-07-27 18:25 ` [PATCH 2/8] libkms: remove explicit define _FILE_OFFSET_BITS 64 Emil Velikov
2014-07-27 18:25 ` [PATCH 3/8] libdrm, freedreno, intel, nouveau, radeon: add Makefile.sources Emil Velikov
2014-07-27 18:25 ` [PATCH 4/8] libdrm,intel: Add Android build Emil Velikov
2014-07-27 18:25 ` [PATCH 5/8] libdrm,intel: rework android header handling Emil Velikov
2014-07-27 18:25 ` [PATCH 6/8] radeon: add Android build support Emil Velikov
2014-07-27 18:25 ` [PATCH 7/8] nouveau: " Emil Velikov
2014-07-27 18:25 ` [PATCH 8/8] freedreno: " Emil Velikov
2014-07-28 2:48 ` [PATCH 0/8] Upstreaming the Android build and misc fixes Emil Velikov
2014-07-28 7:07 ` Daniel Vetter
2014-07-28 12:01 ` Emil Velikov
2014-07-28 15:22 ` Daniel Vetter
2014-07-29 16:14 ` Gore, Tim
2014-07-29 17:10 ` Emil Velikov
2014-07-29 17:27 ` [PATCHv2 " Emil Velikov
2014-07-29 17:27 ` [PATCH 1/8] all: include config.h only when available and use its defines Emil Velikov
2014-07-29 17:27 ` [PATCH 2/8] libkms: remove explicit define _FILE_OFFSET_BITS 64 Emil Velikov
2014-07-29 17:27 ` [PATCH 3/8] libdrm, freedreno, intel, nouveau, radeon: add Makefile.sources Emil Velikov
2014-08-24 18:28 ` [PATCHv3 " Emil Velikov
2014-07-29 17:27 ` [PATCH 4/8] libdrm,intel: Add Android build Emil Velikov
2014-07-29 17:27 ` [PATCH 5/8] libdrm,intel: rework android header handling Emil Velikov
2014-07-29 17:27 ` [PATCH 6/8] radeon: add Android build support Emil Velikov
2014-07-29 17:27 ` [PATCH 7/8] nouveau: " Emil Velikov
2014-07-29 17:27 ` [PATCH 8/8] freedreno: " Emil Velikov
2014-07-31 15:33 ` [PATCHv2 0/8] Upstreaming the Android build and misc fixes Gore, Tim
2014-07-31 18:32 ` Emil Velikov
2014-08-24 18:39 ` Emil Velikov
2014-08-29 9:44 ` Gore, Tim
2014-08-29 10:02 ` Emil Velikov [this message]
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=54004FCD.8060701@gmail.com \
--to=emil.l.velikov@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=tim.gore@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).