From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH v2 00/54] Jentrho-next pull request
Date: Thu, 31 Dec 2015 14:56:44 +0100 [thread overview]
Message-ID: <20151231135644.GA2255@jama> (raw)
In-Reply-To: <cover.1450888554.git.akuster808@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 581 bytes --]
On Wed, Dec 23, 2015 at 08:39:59AM -0800, Armin Kuster wrote:
> Please consider these changes for Jethro-next
>
> I dropped the netmap changes but add more.
>
> mcelog: remove bashism and create ptest subpackage
mcelog is completely broken in jethro, because mcelog-inject is missing
there, I'll add:
commit 906cb0dcf0d40893849b5bd76189b119e9a6c7dc
Author: Kai Kang <kai.kang@windriver.com>
Date: Fri Dec 4 15:09:15 2015 +0800
mce-inject: add recipe
Add recipe of mce-inject which is required to run mcelog ptest
cases.
to this patchset.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
prev parent reply other threads:[~2015-12-31 13:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-23 16:39 [PATCH v2 00/54] Jentrho-next pull request Armin Kuster
2015-12-24 2:32 ` Khem Raj
2015-12-26 1:01 ` akuster808
2015-12-30 12:05 ` Martin Jansa
2015-12-31 13:56 ` Martin Jansa [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=20151231135644.GA2255@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox