From: Scott Garman <scott.a.garman@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: linux-dtb: add multi-dtb build support
Date: Thu, 05 Jul 2012 15:07:24 -0700 [thread overview]
Message-ID: <4FF6101C.1070104@intel.com> (raw)
In-Reply-To: <CAEsOVNeMe1CQEj4V6et+uUsEct0HEETLs6yFL03YteBQyywT_A@mail.gmail.com>
On 07/05/2012 02:37 PM, McClintock Matthew-B29882 wrote:
> On Thu, Jul 5, 2012 at 4:33 PM, Scott Garman <scott.a.garman@intel.com> wrote:
>> On 07/05/2012 01:52 PM, McClintock Matthew-B29882 wrote:
>>>
>>> On Thu, Jul 5, 2012 at 2:59 PM, Scott Garman <scott.a.garman@intel.com>
>>> wrote:
>>>>
>>>> On 07/05/2012 11:29 AM, McClintock Matthew-B29882 wrote:
>>>>>
>>>>>
>>>>> Can we add this to denzil branch? (post 1.2.1 is fine) - I realize
>>>>> this is somewhat a new feature though but it would be helpful to have
>>>>> it in denzil.
>>>>
>>>>
>>>>
>>>> Ok, I've now created a contrib branch to start tracking changes for
>>>> 1.2.2,
>>>> and have included this commit:
>>>>
>>>>
>>>> http://git.openembedded.org/openembedded-core-contrib/log/?h=sgarman/denzil-next-1.2.2
>>>>
>>>> The usual caveats apply - I can rebase this branch at any time, etc.
>>>
>>>
>>> Are you missing a patch on this series? ChecksumError class does not
>>> exist...
>>>
>>> commit 2f009e5b?
>>
>>
>> What is the title of that commit? I'm not seeing it.
>
> $ git show 2f009e5b
> commit 2f009e5b1e4e0a4148ab7d5c60bf0e7a193faa2e
> Author: Richard Purdie <richard.purdie@linuxfoundation.org>
> Date: Sun May 13 12:00:45 2012 +0000
>
> bitbake/fetch2: Improve visibility of checksum warnings when
> fetching from mirrors
>
> When fetching from mirrors, checksum errors would get buried in the
> logs. This raises their profile so a warning is logged on the console
> when fetcher checksum issues are encountered, even if other attempts
> are made to get the file (which may or may not have the same issue).
>
> (Bitbake rev: d43fafd7f01b5534499b45213197d8ccececdbc4)
>
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Ok, this applies then to the poky-based tree, not the oe-core one.
I just tried merging this in but I get conflicts with one of Khem's
patches. I'm leaving imminently for vacation so I will take a closer
look at this early next week.
Scott
--
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center
next prev parent reply other threads:[~2012-07-05 22:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-26 3:53 linux-dtb: add multi-dtb build support b19537
2012-06-28 17:12 ` Saul Wold
2012-07-05 18:29 ` McClintock Matthew-B29882
2012-07-05 19:38 ` Scott Garman
2012-07-05 19:59 ` Scott Garman
2012-07-05 20:52 ` McClintock Matthew-B29882
2012-07-05 21:33 ` Scott Garman
2012-07-05 21:37 ` McClintock Matthew-B29882
2012-07-05 22:07 ` Scott Garman [this message]
2012-07-20 14:43 ` McClintock Matthew-B29882
2012-07-16 22:48 ` Saul Wold
2012-07-16 22:50 ` McClintock Matthew-B29882
2012-07-20 14:42 ` McClintock Matthew-B29882
2012-08-20 6:10 ` Luo Zhenhua-B19537
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=4FF6101C.1070104@intel.com \
--to=scott.a.garman@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.