From: Saul Wold <saul.wold@intel.com>
To: Darren Hart <dvhart@linux.intel.com>
Cc: poky@yoctoproject.org
Subject: Re: [PATCH 0/1] kernel-rt: fix build issues
Date: Wed, 27 Apr 2011 17:56:12 -0700 [thread overview]
Message-ID: <4DB8BB2C.8040704@intel.com> (raw)
In-Reply-To: <4DB8A220.6040806@linux.intel.com>
On 04/27/2011 04:09 PM, Darren Hart wrote:
>
>
> On 04/19/2011 06:18 PM, Richard Purdie wrote:
>> On Tue, 2011-04-19 at 17:02 -0700, Darren Hart wrote:
>>> From: Darren Hart<dvhart@linux.intel.com>
>>>
>>> The linux-yocto-rt recipe wasn't building in master or bernard. This brings the
>>> recipe up to date with the linux-yocto* recipes and corrects the build failures.
>>> This patch should be applied to both bernard and master.
>>>
>>> Pull URL: git://git.pokylinux.org/poky-contrib.git
>>> Branch: dvhart/bernard/rt
>>> Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=dvhart/bernard/rt
>>>
>>> Thanks,
>>> Darren Hart<dvhart@linux.intel.com>
>>> ---
>>>
>>>
>>> Darren Hart (1):
>>> kernel-rt: use correct branch names and new git SRC_REV format
>>
>> Merged to master, thanks.
>
> Can we also merge to Bernard please? Without it, meta-rt will not build.
>
Staged into the stage/bernard area.
Sau!
> --
> Darren
>
>>
>> Richard
>>
>> _______________________________________________
>> poky mailing list
>> poky@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/poky
>
prev parent reply other threads:[~2011-04-28 0:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-20 0:02 [PATCH 0/1] kernel-rt: fix build issues Darren Hart
2011-04-20 0:02 ` [PATCH 1/1] kernel-rt: use correct branch names and new git SRC_REV format Darren Hart
2011-04-20 1:18 ` [PATCH 0/1] kernel-rt: fix build issues Richard Purdie
2011-04-27 23:09 ` Darren Hart
2011-04-28 0:56 ` Saul Wold [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=4DB8BB2C.8040704@intel.com \
--to=saul.wold@intel.com \
--cc=dvhart@linux.intel.com \
--cc=poky@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