All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: "Hongzhi.Song" <hongzhi.song@windriver.com>
Cc: openembeded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-oe][PATCH v4 0/1] Add a recipe about kernel selftest
Date: Sun, 5 Aug 2018 18:35:09 -0700	[thread overview]
Message-ID: <CAMKF1spCit8YhDJuVN07BoP=m5hS+gg=3HFgCsN48HJJXY7QNg@mail.gmail.com> (raw)
In-Reply-To: <69958f41-e2d9-8189-aca9-3c8128a4bee1@windriver.com>

On Sun, Aug 5, 2018 at 6:29 PM Hongzhi, Song <hongzhi.song@windriver.com> wrote:
>
> ping

its still failing for


qemuarm
http://jenkins.nas-admin.org/view/OE/job/oe_world_qemuarm/838/console

qemuarm64

http://jenkins.nas-admin.org/view/OE/job/oe_world_qemuarm64/111/console

qemux86

http://jenkins.nas-admin.org/view/OE/job/oe_world_qemux86/839/console

qemux86-64

http://jenkins.nas-admin.org/view/OE/job/oe_world_qemux86-64/792/console

you can look at jenkins jobs or patchwork for latest status of the patches.
>
> --Hongzhi
>
>
> On 2018年08月01日 16:32, Hongzhi.Song wrote:
> > v4:
> >     add the optimization level of compiler, when define _FORTIFY_SOURCE
> >
> > v3:
> >      add support for musl when build bpf and modify the recipe slightly
> >
> > Hongzhi.Song (1):
> >    kernel-selftest: Add a recipe on kernel selftest
> >
> >   .../kernel-selftest/kernel-selftest.bb             | 104 ++++++
> >   ...bpf-test_progs.c-add-support-for-musllibc.patch |  25 ++
> >   ...-swap.h-micro-define-to-support-musl-libc.patch |  26 ++
> >   .../kernel-selftest/kernel-selftest/COPYING        | 356 +++++++++++++++++++++
> >   .../kernel-selftest/userfaultfd.patch              | 322 +++++++++++++++++++
> >   5 files changed, 833 insertions(+)
> >   create mode 100644 meta-oe/recipes-kernel/kernel-selftest/kernel-selftest.bb
> >   create mode 100644 meta-oe/recipes-kernel/kernel-selftest/kernel-selftest/0001-bpf-test_progs.c-add-support-for-musllibc.patch
> >   create mode 100644 meta-oe/recipes-kernel/kernel-selftest/kernel-selftest/0001-swap.h-micro-define-to-support-musl-libc.patch
> >   create mode 100644 meta-oe/recipes-kernel/kernel-selftest/kernel-selftest/COPYING
> >   create mode 100644 meta-oe/recipes-kernel/kernel-selftest/kernel-selftest/userfaultfd.patch
> >
>


      reply	other threads:[~2018-08-06  1:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-01  8:32 [meta-oe][PATCH v4 0/1] Add a recipe about kernel selftest Hongzhi.Song
2018-08-01  8:32 ` [meta-oe][PATCH v4] kernel-selftest: Add a recipe on " Hongzhi.Song
2018-08-03  9:01 ` [meta-oe][PATCH v4 0/1] Add a recipe about " Hongzhi, Song
2018-08-06  1:32 ` Hongzhi, Song
2018-08-06  1:35   ` Khem Raj [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='CAMKF1spCit8YhDJuVN07BoP=m5hS+gg=3HFgCsN48HJJXY7QNg@mail.gmail.com' \
    --to=raj.khem@gmail.com \
    --cc=hongzhi.song@windriver.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 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.