From: cel@kernel.org
To: <kdevops@lists.linux.dev>
Cc: Chuck Lever <chuck.lever@oracle.com>
Subject: [PATCH] linux: Edit cel-linux.yaml
Date: Fri, 28 Jun 2024 17:20:09 -0400 [thread overview]
Message-ID: <20240628212009.1548807-1-cel@kernel.org> (raw)
From: Chuck Lever <chuck.lever@oracle.com>
Add the nfsd-testing testing branch, and correct a typo.
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
---
workflows/linux/refs/default/Kconfig.cel-linux | 12 +++++++++---
workflows/linux/refs/static/cel-linux.yaml | 8 ++++++--
2 files changed, 15 insertions(+), 5 deletions(-)
I'm having some trouble getting this new infrastructure to work.
"make menuconfig" leaves this line in .config:
CONFIG_BOOTLINUX_TREE_REF="BOOTLINUX_TREE_CEL_REF"
And then "make bringup" fails to clone Linux because that's not a
valid ref.
diff --git a/workflows/linux/refs/default/Kconfig.cel-linux b/workflows/linux/refs/default/Kconfig.cel-linux
index 692236e94dbd..56071e65328b 100644
--- a/workflows/linux/refs/default/Kconfig.cel-linux
+++ b/workflows/linux/refs/default/Kconfig.cel-linux
@@ -12,9 +12,14 @@ config BOOTLINUX_TREE_CEL_LINUX_REF_NEXT
Pull the nfsd-next branch.
config BOOTLINUX_TREE_CEL_LINUX_REF_FIXES
- bool "nfsd-fixed"
+ bool "nfsd-fixes"
help
- Pull the nfsd-fixed branch.
+ Pull the nfsd-fixes branch.
+
+config BOOTLINUX_TREE_CEL_LINUX_REF_TESTING
+ bool "nfsd-testing"
+ help
+ Pull the nfsd-testing branch.
config BOOTLINUX_TREE_CEL_LINUX_REF_CUSTOM
bool "custom"
@@ -26,7 +31,8 @@ endchoice
config BOOTLINUX_TREE_CEL_LINUX_REF
string
default "nfsd-next" if BOOTLINUX_TREE_CEL_LINUX_REF_NEXT
- default "nfsd-fixed" if BOOTLINUX_TREE_CEL_LINUX_REF_FIXES
+ default "nfsd-fixes" if BOOTLINUX_TREE_CEL_LINUX_REF_FIXES
+ default "nfsd-testing" if BOOTLINUX_TREE_CEL_LINUX_REF_TESTING
default BOOTLINUX_CEL_LINUX_CUSTOM_REF_NAME if BOOTLINUX_TREE_CEL_LINUX_REF_CUSTOM
endif # !HAVE_BOOTLINUX_TREE_CEL_LINUX_USER_REFS
diff --git a/workflows/linux/refs/static/cel-linux.yaml b/workflows/linux/refs/static/cel-linux.yaml
index bba35efb8214..8b94b9f3449c 100644
--- a/workflows/linux/refs/static/cel-linux.yaml
+++ b/workflows/linux/refs/static/cel-linux.yaml
@@ -6,8 +6,12 @@ configs:
help: "Pull the nfsd-next branch."
- fixes:
config: BOOTLINUX_TREE_CEL_LINUX_REF_FIXES
- ref: "nfsd-fixed"
- help: "Pull the nfsd-fixed branch."
+ ref: "nfsd-fixes"
+ help: "Pull the nfsd-fixes branch."
+ - testing:
+ config: BOOTLINUX_TREE_CEL_LINUX_REF_TESTING
+ ref: "nfsd-testing"
+ help: "Pull the nfsd-testing branch."
- custom:
config: BOOTLINUX_TREE_CEL_LINUX_REF_CUSTOM
ref: BOOTLINUX_CEL_LINUX_CUSTOM_REF_NAME
--
2.45.2
next reply other threads:[~2024-06-28 21:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-28 21:20 cel [this message]
2024-06-29 21:29 ` [PATCH] linux: Edit cel-linux.yaml Chuck Lever
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=20240628212009.1548807-1-cel@kernel.org \
--to=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=kdevops@lists.linux.dev \
/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