From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Robert Yang <liezhi.yang@windriver.com>
Cc: paul.eggleton@linux.intel.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 000/122 V2] [dora] fixes for dora (cover leter only)
Date: Fri, 13 Dec 2013 09:26:29 +0000 [thread overview]
Message-ID: <1386926789.20901.20.camel@ted> (raw)
In-Reply-To: <52AAA463.5040100@windriver.com>
On Fri, 2013-12-13 at 14:08 +0800, Robert Yang wrote:
>
> On 12/13/2013 07:34 AM, Richard Purdie wrote:
> > On Thu, 2013-12-12 at 14:49 +0800, Robert Yang wrote:
> >
> > Other than the patches I've mentioned, things should be merged in the
> > dora branch. We've found some build issues. I've pushed a fix for the
> > qt3 one, we also have one with lttng-modules which we don't have a fix
> > for yet.
> >
>
> Hi RP,
>
> For the failure of lttng-modules, it seemed the auto builder didn't take
> the patches that I had sent to poky@yoctoproject.org:
>
> [poky] [PATCH 2/3] [dora] meta-yocto-bsp: update SRCREVs for 3.10.17 and
> beagleboard fixes
>
> Would you please help to merge it (them) ?
>
> The branch robert/dora-next-oecore only contains the patches for oe-core,
> while the robert/dora-next contains patches for bitbake, oe-core and
> meta-yoctoX, I'm sorry that I didn't explain this clearly.
Sorry I missed the meta-yocto changes. I've merged these now.
Cheers,
Richard
next prev parent reply other threads:[~2013-12-13 9:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 9:21 [PATCH 000/122 V2] [dora] fixes for dora (cover leter only) Robert Yang
2013-12-11 14:26 ` Richard Purdie
2013-12-11 14:38 ` Richard Purdie
2013-12-11 17:18 ` Mark Hatle
2013-12-12 6:49 ` Robert Yang
2013-12-12 23:34 ` Richard Purdie
2013-12-12 23:43 ` Steve Sakoman
2013-12-13 2:02 ` Robert Yang
2013-12-13 2:00 ` Robert Yang
2013-12-13 6:08 ` Robert Yang
2013-12-13 9:26 ` Richard Purdie [this message]
2013-12-11 16:51 ` Saul Wold
2013-12-12 6:51 ` Robert Yang
2013-12-12 9:01 ` Robert Yang
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=1386926789.20901.20.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=liezhi.yang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.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