From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Seebs <seebs@seebs.net>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] pseudo: update to latest master
Date: Mon, 19 Feb 2018 20:37:46 +0200 [thread overview]
Message-ID: <51d19b57-0054-0401-b939-b51325db47f7@linux.intel.com> (raw)
In-Reply-To: <20180219115538.5081767b@seebsdell>
On 02/19/2018 07:55 PM, Seebs wrote:
> This gets back to "and one of the problems with testing is that
> if I don't actually check the logs, I often don't see problems",
> because pseudo does enough internal disaster recovery that things can
> explode horribly without observable failures.
>
> Now extracting the data.u64 value and using that consistently as the
> index. Pushed fix to master.
Thanks; with this change things seem to work again on my side. I've
updated and force pushed the branch on poky-contrib, so please test.
I'll be on holiday until next Tuesday.
http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=akanavin/pseudo-1.9.0
Alex
next prev parent reply other threads:[~2018-02-19 18:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-16 9:56 [PATCH] pseudo: update to latest master Alexander Kanavin
2018-02-16 16:55 ` Martin Jansa
2018-02-16 17:26 ` Alexander Kanavin
2018-02-16 17:51 ` Seebs
2018-02-16 19:11 ` Martin Jansa
2018-02-16 19:25 ` Seebs
2018-02-17 11:22 ` Alexander Kanavin
2018-02-17 11:56 ` Martin Jansa
2018-02-17 12:03 ` Martin Jansa
2018-02-17 13:28 ` Alexander Kanavin
2018-02-17 20:17 ` Seebs
2018-02-18 11:43 ` Martin Jansa
2018-02-18 20:23 ` Martin Jansa
2018-02-19 9:38 ` Alexander Kanavin
2018-02-19 9:27 ` Alexander Kanavin
2018-02-19 17:55 ` Seebs
2018-02-19 18:37 ` Alexander Kanavin [this message]
2018-02-19 19:01 ` Martin Jansa
2018-02-19 19:36 ` Seebs
-- strict thread matches above, loose matches on Subject: below --
2018-03-01 13:53 Alexander Kanavin
2018-03-01 15:06 ` Seebs
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=51d19b57-0054-0401-b939-b51325db47f7@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=seebs@seebs.net \
/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