From: Joao Pinto <Joao.Pinto@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] Buildroot' patch to add support for aarch64 in mplayer configure script
Date: Wed, 16 Sep 2015 09:28:44 +0100 [thread overview]
Message-ID: <55F9283C.1070709@synopsys.com> (raw)
In-Reply-To: <55F88C33.1070503@mind.be>
Hi Arnout!
On 9/15/2015 10:22 PM, Arnout Vandecappelle wrote:
> On 15-09-15 23:18, Thomas Petazzoni wrote:
>> Hello Joao,
>>
>> Your e-mail is two patches concataned to each other. Can you make that
>> a single patch instead?
>>
>> Also, the title should be adjusted, as I explained in a previous
>> message. See some more comments below.
>>
>> On Tue, 15 Sep 2015 18:00:48 +0100, jpinto wrote:
>>>
>>> Signed-off-by: Joao Pinto <jpinto@synopsys.com>
>>> Tested-by: Joao Pinto <jpinto@synopsys.com>
>>> ---
>>> package/mplayer/0007-enable-aarch64.patch | 13 +++++++++++++
>>> 1 file changed, 13 insertions(+)
>>> create mode 100644 package/mplayer/0007-enable-aarch64.patch
>>>
>>> diff --git a/package/mplayer/0007-enable-aarch64.patch b/package/mplayer/0007-enable-aarch64.patch
>>> new file mode 100644
>>> index 0000000..7f75756
>>> --- /dev/null
>>> +++ b/package/mplayer/0007-enable-aarch64.patch
>>> @@ -0,0 +1,13 @@
>>
>> All patches in Buildroot should have a description and a Signed-off-by
>> line. See
>> http://buildroot.org/downloads/manual/manual.html#_format_and_licensing_of_the_package_patches
>> for details.
>
> Once that is done, could you also send the patch upstream?
When you say upstream, you mean send it to mplayer authors?
>
> Regards,
> Arnout
>
>
Regards,
Joao
next prev parent reply other threads:[~2015-09-16 8:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-15 17:00 [Buildroot] [PATCH v2] Buildroot' patch to add support for aarch64 in mplayer configure script jpinto
2015-09-15 21:18 ` [Buildroot] [PATCH v3] " Thomas Petazzoni
2015-09-15 21:22 ` Arnout Vandecappelle
2015-09-16 8:28 ` Joao Pinto [this message]
2015-09-16 8:42 ` Thomas Petazzoni
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=55F9283C.1070709@synopsys.com \
--to=joao.pinto@synopsys.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