From: akuster808 <akuster808@gmail.com>
To: "Daniel Díaz" <daniel.diaz@linaro.org>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [morty][PATCH 1/2] glibc: add missing TRAP_BRANCH/TRAP_HWBKPT definitions
Date: Tue, 26 Jun 2018 15:33:38 -0700 [thread overview]
Message-ID: <3c778e17-bb7f-e934-e3ce-6f969defdac9@gmail.com> (raw)
In-Reply-To: <CAEUSe7-NkJJR=ppBd5AoahaRygd4CrcbwgeLTo5VLcWXEiiX2w@mail.gmail.com>
On 06/18/2018 12:20 PM, Daniel Díaz wrote:
> Hello!
>
>
> On 11 June 2018 at 16:46, Andre McCurdy <armccurdy@gmail.com> wrote:
>> On Mon, Jun 11, 2018 at 2:38 PM, akuster808 <akuster808@gmail.com> wrote:
>>> On 06/11/2018 10:30 AM, Daniel Díaz wrote:
>>>> Ping on this series for Morty.
>>> this is in the stable/morty-next branch which is on hold for the current
>>> morty QA.
>>> http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=stable/pyro-next&id=76ffc6b7e5ff6f2bab6e53bb07f52a25fcb81ac9
>> That's a link for stable/pyro-next.
>> The change doesn't seem to be in stable/morty-next though:
>> http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=stable/morty-next
> Is there anything from my side that needs to be done for this patch?
Nope. I have it in the stable/moryt mut branch and trying to address
build issues.
- armin
>
> Thanks and greetings!
>
> Daniel Díaz
> daniel.diaz@linaro.org
next prev parent reply other threads:[~2018-06-26 22:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-06 17:08 [morty][PATCH 1/2] glibc: add missing TRAP_BRANCH/TRAP_HWBKPT definitions Daniel Díaz Rodríguez
2018-04-06 20:43 ` akuster808
2018-05-16 21:20 ` Daniel Díaz
2018-06-11 17:30 ` Daniel Díaz
2018-06-11 21:38 ` akuster808
2018-06-11 21:46 ` Andre McCurdy
2018-06-18 19:20 ` Daniel Díaz
2018-06-26 22:33 ` akuster808 [this message]
2018-06-26 22:54 ` Andre McCurdy
2018-06-26 23:10 ` akuster808
-- strict thread matches above, loose matches on Subject: below --
2018-03-13 16:17 Daniel Díaz
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=3c778e17-bb7f-e934-e3ce-6f969defdac9@gmail.com \
--to=akuster808@gmail.com \
--cc=daniel.diaz@linaro.org \
--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