public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@denx.de>
To: Chris Paterson <chris.paterson2@renesas.com>
Cc: Pavel Machek <pavel@denx.de>, cip-dev@lists.cip-project.org
Subject: Re: [PATCH 4.4.y-st] gitlab-ci: Add configuration for CIP's GitLab CI pipelines
Date: Fri, 11 Nov 2022 08:38:27 +0100	[thread overview]
Message-ID: <Y23783UalLmLHzbr@duo.ucw.cz> (raw)
In-Reply-To: <20221011144940.24071-1-chris.paterson2@renesas.com>

[-- Attachment #1: Type: text/plain, Size: 958 bytes --]

Hi!

> Actual pipelines are defined externally [0] to save on churn in the kernel
> tree.
> 
> [0] https://gitlab.com/cip-project/cip-testing/linux-cip-pipelines

Thank you, applied to -st-rc tree.

Best regards,
									Pavel

> Signed-off-by: Chris Paterson <chris.paterson2@renesas.com>
> ---
>  .gitlab-ci.yml | 3 +++
>  1 file changed, 3 insertions(+)
>  create mode 100644 .gitlab-ci.yml
> 
> diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
> new file mode 100644
> index 000000000000..ad0593601dbb
> --- /dev/null
> +++ b/.gitlab-ci.yml
> @@ -0,0 +1,3 @@
> +include:
> +  - https://gitlab.com/cip-project/cip-testing/linux-cip-pipelines/raw/master/linux-cip-pipeline.yml
> +  - https://gitlab.com/cip-project/cip-testing/linux-cip-pipelines/raw/master/trees/linux-4.4.y-st.yml

-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

      reply	other threads:[~2022-11-11  7:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-11 14:49 [PATCH 4.4.y-st] gitlab-ci: Add configuration for CIP's GitLab CI pipelines Chris Paterson
2022-11-11  7:38 ` Pavel Machek [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=Y23783UalLmLHzbr@duo.ucw.cz \
    --to=pavel@denx.de \
    --cc=chris.paterson2@renesas.com \
    --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