All of lore.kernel.org
 help / color / mirror / Atom feed
From: pavel@denx.de (Pavel Machek)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] [ANNOUNCE] Release v4.19.88-cip16 and v4.4.206-cip40
Date: Mon, 16 Dec 2019 12:22:46 +0100	[thread overview]
Message-ID: <20191216112246.GA17029@amd> (raw)
In-Reply-To: <OSAPR01MB323483390F138C52C363126492540@OSAPR01MB3234.jpnprd01.prod.outlook.com>

Hi!

> CIP kernel team has released Linux kernel v4.19.88-cip16 and v4.4.206-cip40.
> The linux-4.19.y-cip tree has been updated base version from 4.19.85 to 4.19.88,
> and The linux-4.4.y-cip tree has been updated base version from 4.4.199 to 4.4.206.

>   v4.4.206-cip40:
>     repository:
>       https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git
>     branch:
>       linux-4.4.y-cip
>     commit:
>       0cddb349320426954582511b95e7d31873941aad

I attempted to get this tested, but failed:

https://gitlab.com/cip-project/cip-kernel/linux-cip/pipelines/103361420

Found errors in your .gitlab-ci.yml:
Resolving config took longer than expected
You can also test your .gitlab-ci.yml in CI Lint

Best regards,
								Pavel
-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20191216/460722e2/attachment.sig>

  parent reply	other threads:[~2019-12-16 11:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-13 22:21 [cip-dev] [ANNOUNCE] Release v4.19.88-cip16 and v4.4.206-cip40 nobuhiro1.iwamatsu at toshiba.co.jp
2019-12-16 11:14 ` [cip-dev] gitlab mirroring broken was " Pavel Machek
2019-12-16 11:27   ` Chris Paterson
2019-12-16 11:22 ` Pavel Machek [this message]
2019-12-16 11:26   ` [cip-dev] " Chris Paterson
2019-12-16 11:35     ` Chris Paterson

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=20191216112246.GA17029@amd \
    --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 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.