From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Martin Jansa <martin.jansa@gmail.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Daniel Lublin <daniel@lublin.se>, Pavel Modilaynen <pavelmn@axis.com>
Subject: Re: [morty][PATCH] buildstats.bbclass: Avoid index exception in /proc/PID/io parsing
Date: Sun, 04 Mar 2018 13:20:55 +0000 [thread overview]
Message-ID: <1520169655.3436.64.camel@linuxfoundation.org> (raw)
In-Reply-To: <CA+chaQfHzRvmJCGzsDht2tJwyMuVP01oM4Uorf83kUS3_1TAVA@mail.gmail.com>
On Sun, 2018-03-04 at 12:41 +0100, Martin Jansa wrote:
> ping
I've queued this and the other morty patch in morty-next. Looks like
we'll need to do further rounds of testing.
Cheers,
Richard
prev parent reply other threads:[~2018-03-04 13:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 19:10 [morty][PATCH] buildstats.bbclass: Avoid index exception in /proc/PID/io parsing Martin Jansa
2018-03-04 11:41 ` Martin Jansa
2018-03-04 13:20 ` 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=1520169655.3436.64.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=daniel@lublin.se \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=pavelmn@axis.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