From: richard.purdie@linuxfoundation.org
To: "Reyna, David" <david.reyna@windriver.com>,
"toaster@yoctoproject.org" <toaster@yoctoproject.org>
Subject: Re: Toaster enhancement set posted
Date: Tue, 17 Jul 2018 13:53:13 +0100 [thread overview]
Message-ID: <854d63a8511d33aa962898fdc3fa01c144972993.camel@linuxfoundation.org> (raw)
In-Reply-To: <5E53D14CE4667A45B9A06760DE5D13D0F3920B91@ALA-MBD.corp.ad.wrs.com>
On Mon, 2018-07-16 at 17:58 +0000, Reyna, David wrote:
> I have been doing additional testing, and will have the post for you
> this week.
>
> After that, I have a patch set from Awais Belal that I am testing,
> and will merge on top of the current work and then submit that.
>
> Thank you for asking!
Thanks, I've dropped the patch I was carrying in bitbake's master-next
and will await the new patch.
Cheers,
Richard
prev parent reply other threads:[~2018-07-17 12:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-28 2:10 Toaster enhancement set posted Reyna, David
2018-06-28 13:44 ` Richard Purdie
2018-06-29 8:37 ` Reyna, David
2018-07-16 17:00 ` Richard Purdie
2018-07-16 17:58 ` Reyna, David
2018-07-17 12:53 ` richard.purdie [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=854d63a8511d33aa962898fdc3fa01c144972993.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=david.reyna@windriver.com \
--cc=toaster@yoctoproject.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).