All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roman Stratiienko <roman.stratiienko@globallogic.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: xenomai@xenomai.org
Subject: Re: [PATCH v3] travis: add basic CI support
Date: Mon, 18 Mar 2019 18:47:05 +0200	[thread overview]
Message-ID: <CAODwZ7u6sRRVmE76-iP0rjp6+WSpaGwCsRaumuZAaq1yaDzMaQ@mail.gmail.com> (raw)
In-Reply-To: <2e814509-3d89-efd4-476c-fdcefc989b16@siemens.com>

On Mon, Mar 18, 2019 at 5:39 PM Jan Kiszka <jan.kiszka@siemens.com> wrote:

> On 18.03.19 15:24, Jan Kiszka wrote:
> > On 18.03.19 15:21, Roman Stratiienko wrote:
> >> Hello Jan,
> >>
> >> Build failure is caused by "cobalt: Add sched-quota tracepoints".
> >> I had to revert it to continue with testing
> >>
> >
> > Ah, that's a good trace.  We might be missing some include... One
> minute...
> >
>
> All green now with v2 of my tracepoint patch.
>
> So we can move forward: Any updates on the fixes for newer kernels?
>


Currently not. I started to make clean port of ipipe-noarch onto 4.19, so I
hope to open it for review soon.


>
> Jan
>
> --
> Siemens AG, Corporate Technology, CT RDA IOT SES-DE
> Corporate Competence Center Embedded Linux
>

  reply	other threads:[~2019-03-18 16:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-11 14:37 [PATCH] kernel: cobalt: replace access_ok with corresponding wrappers roman.stratiienko
2019-03-11 14:37 ` [PATCH v3] travis: add basic CI support roman.stratiienko
2019-03-18 12:59   ` Jan Kiszka
2019-03-18 13:25     ` Jan Kiszka
2019-03-18 14:21       ` Roman Stratiienko
2019-03-18 14:24         ` Jan Kiszka
2019-03-18 15:39           ` Jan Kiszka
2019-03-18 16:47             ` Roman Stratiienko [this message]
2019-03-18 16:51               ` Jan Kiszka
2019-03-18 17:22                 ` Roman Stratiienko
2019-03-18 17:45                   ` Philippe Gerum
2019-03-19 20:03 ` [PATCH] kernel: cobalt: replace access_ok with corresponding wrappers Jan Kiszka

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=CAODwZ7u6sRRVmE76-iP0rjp6+WSpaGwCsRaumuZAaq1yaDzMaQ@mail.gmail.com \
    --to=roman.stratiienko@globallogic.com \
    --cc=jan.kiszka@siemens.com \
    --cc=xenomai@xenomai.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.