From: Pavel Machek <pavel@denx.de>
To: Pavel Machek <pavel@denx.de>
Cc: cip-dev@lists.cip-project.org
Subject: Re: [cip-dev] 4.19.106-cip21-rt8 problems on de0-nano
Date: Tue, 3 Mar 2020 10:23:43 +0100 [thread overview]
Message-ID: <20200303092343.GA11594@duo.ucw.cz> (raw)
In-Reply-To: <20200303091556.GA10040@duo.ucw.cz>
[-- Attachment #1.1: Type: text/plain, Size: 562 bytes --]
On Tue 2020-03-03 10:15:56, Pavel Machek wrote:
> Hi!
>
> I pushed candidate for -cip-rt, but it seems to fail on de0-nano
> board. Code under testing is at:
>
> https://gitlab.com/cip-project/cip-kernel/linux-cip/tree/ci/pavel/linux-cip
It is pipeline
https://gitlab.com/cip-project/cip-kernel/linux-cip/pipelines/122762401
I'll reuse the branch for more testing.
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
cip-dev mailing list
cip-dev@lists.cip-project.org
https://lists.cip-project.org/mailman/listinfo/cip-dev
next prev parent reply other threads:[~2020-03-03 9:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-03 9:15 [cip-dev] 4.19.106-cip21-rt8 problems on de0-nano Pavel Machek
2020-03-03 9:23 ` Pavel Machek [this message]
2020-03-03 17:10 ` Pavel Machek
2020-03-03 21:28 ` Pavel Machek
2020-03-04 19:53 ` Jan Kiszka
2020-03-09 10:21 ` [cip-dev] I need de0-nano testing for -rt release was " Pavel Machek
2020-03-09 18:52 ` Jan Kiszka
2020-03-10 16:50 ` Bhola, Bikram
[not found] ` <78fd4f1df8034021ae195b8287cf2f29@SVR-IES-MBX-03.mgc.mentorg.com>
2020-03-11 15:36 ` Bhola, Bikram
2020-03-15 9:42 ` [cip-dev] " Pavel Machek
2020-03-16 11:59 ` Pavel Machek
2020-03-16 16:05 ` Bhola, Bikram
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=20200303092343.GA11594@duo.ucw.cz \
--to=pavel@denx.de \
--cc=cip-dev@lists.cip-project.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