From: Mike Looijmans <mike.looijmans@topic.nl>
To: akuster808 <akuster808@gmail.com>, Nathan Rossi <nathan@nathanrossi.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH][Morty] binutils-2.27.inc: Fix alignment frags for aarch64
Date: Tue, 24 Jan 2017 07:48:57 +0100 [thread overview]
Message-ID: <1efda273-0a0f-e75d-1364-6ac1815154fe@topic.nl> (raw)
In-Reply-To: <ee6f0244-0fb1-ad27-6056-a358b5eb0112@gmail.com>
On 18-01-17 17:09, akuster808 wrote:
>
>
> On 01/18/2017 04:08 AM, Nathan Rossi wrote:
>> On 18 January 2017 at 19:37, Mike Looijmans <mike.looijmans@topic.nl> wrote:
>>> Could someone at least please say "yes" or "no"?
>>>
>>> I now have three projects waiting for this patch to be included in morty. If
>>> it's not going to happen, I'll have to add a bbappend to these layers to fix
>>> it.
>>>
>>> On 16-01-17 18:49, Manjukumar Harthikote Matha wrote:
>>>> Ping, this has been applied to master
>> Armin, you mentioned on IRC ~1 week ago that you had merged it to your
>> staging branch? Any updates?
>> Also I had a look and could not find the change in
>> http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=akuster/morty-next?
>>
>> Maybe I am looking in the wrong place though for your staging tree?
> I forgot to press go. Its there now.
Much appreciated.
Who's next in line to press "go" now? I still have three projects waiting.
Apparently the ARM64 isn't very popular, no one seems to care about its build
failures...
Kind regards,
Mike Looijmans
System Expert
TOPIC Products
Materiaalweg 4, NL-5681 RJ Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
E-mail: mike.looijmans@topicproducts.com
Website: www.topicproducts.com
Please consider the environment before printing this e-mail
next prev parent reply other threads:[~2017-01-24 6:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-22 21:01 [PATCH][Morty] binutils-2.27.inc: Fix alignment frags for aarch64 Manjukumar Matha
2016-11-22 22:03 ` Khem Raj
2016-11-22 23:08 ` Manjukumar Harthikote Matha
2016-11-22 23:36 ` Khem Raj
2016-11-22 23:36 ` Manjukumar Harthikote Matha
2016-12-15 22:28 ` Manjukumar Harthikote Matha
2016-12-19 13:04 ` Burton, Ross
2016-12-19 13:05 ` Burton, Ross
2016-12-19 21:29 ` Manjukumar Harthikote Matha
2017-01-16 17:49 ` Manjukumar Harthikote Matha
2017-01-18 9:37 ` Mike Looijmans
2017-01-18 12:08 ` Nathan Rossi
2017-01-18 16:09 ` akuster808
2017-01-18 20:16 ` Manjukumar Harthikote Matha
2017-01-24 6:48 ` Mike Looijmans [this message]
2017-01-24 15:45 ` akuster808
2017-01-30 7:18 ` Mike Looijmans
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=1efda273-0a0f-e75d-1364-6ac1815154fe@topic.nl \
--to=mike.looijmans@topic.nl \
--cc=akuster808@gmail.com \
--cc=nathan@nathanrossi.com \
--cc=openembedded-core@lists.openembedded.org \
/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