From: Vignesh Raman <vignesh.raman@collabora.com>
To: helen.koike@collabora.com, airlied@gmail.com, daniel@ffwll.ch
Cc: david.heidelberg@collabora.com, sergi.blanch.torne@collabora.com,
guilherme.gallo@collabora.com, daniels@collabora.com,
gustavo.padovan@collabora.com, emma@anholt.net,
robdclark@gmail.com, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
virtualization@lists.linux-foundation.org,
linux-rockchip@lists.infradead.org,
linux-arm-msm@vger.kernel.org
Subject: [PATCH v4 7/7] drm: ci: Use scripts/config to enable/disable configs
Date: Thu, 14 Sep 2023 14:24:26 +0530 [thread overview]
Message-ID: <20230914085426.883255-8-vignesh.raman@collabora.com> (raw)
In-Reply-To: <20230914085426.883255-1-vignesh.raman@collabora.com>
Instead of modifying files in git to enable/disable
configs, use scripts/config on the .config file which
will be used for building the kernel.
Suggested-by: Jani Nikula <jani.nikula@intel.com>
Acked-by: Helen Koike <helen.koike@collabora.com>
Signed-off-by: Vignesh Raman <vignesh.raman@collabora.com>
---
v2:
- Added a new patch in the series to use scripts/config to enable/disable configs
v3:
- No changes
v4:
- No changes
---
drivers/gpu/drm/ci/build.sh | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/drivers/gpu/drm/ci/build.sh b/drivers/gpu/drm/ci/build.sh
index 58b71538f489..bfe161b47951 100644
--- a/drivers/gpu/drm/ci/build.sh
+++ b/drivers/gpu/drm/ci/build.sh
@@ -70,19 +70,19 @@ if [ -z "$CI_MERGE_REQUEST_PROJECT_PATH" ]; then
fi
fi
-for opt in $ENABLE_KCONFIGS; do
- echo CONFIG_$opt=y >> drivers/gpu/drm/ci/${KERNEL_ARCH}.config
-done
-for opt in $DISABLE_KCONFIGS; do
- echo CONFIG_$opt=n >> drivers/gpu/drm/ci/${KERNEL_ARCH}.config
-done
-
if [[ -n "${MERGE_FRAGMENT}" ]]; then
./scripts/kconfig/merge_config.sh ${DEFCONFIG} drivers/gpu/drm/ci/${MERGE_FRAGMENT}
else
make `basename ${DEFCONFIG}`
fi
+for opt in $ENABLE_KCONFIGS; do
+ ./scripts/config --enable CONFIG_$opt
+done
+for opt in $DISABLE_KCONFIGS; do
+ ./scripts/config --disable CONFIG_$opt
+done
+
make ${KERNEL_IMAGE_NAME}
mkdir -p /lava-files/
--
2.40.1
next prev parent reply other threads:[~2023-09-14 8:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-14 8:54 [PATCH v4 0/7] drm: ci: fixes Vignesh Raman
2023-09-14 8:54 ` [PATCH v4 1/7] drm: ci: igt_runner: Remove todo Vignesh Raman
2023-09-14 8:54 ` [PATCH v4 2/7] drm: ci: Force db410c to host mode Vignesh Raman
2023-09-14 8:54 ` [PATCH v4 3/7] drm: ci: virtio: Update ci variables Vignesh Raman
2023-09-14 8:54 ` [PATCH v4 4/7] drm: ci: Enable regulator Vignesh Raman
2023-09-14 8:54 ` [PATCH v4 5/7] drm: ci: Update xfails Vignesh Raman
2023-09-22 16:36 ` Helen Koike
2023-09-14 8:54 ` [PATCH v4 6/7] drm: ci: Enable new jobs Vignesh Raman
2023-09-14 8:54 ` Vignesh Raman [this message]
2023-09-22 13:53 ` [PATCH v4 0/7] drm: ci: fixes Helen Koike
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=20230914085426.883255-8-vignesh.raman@collabora.com \
--to=vignesh.raman@collabora.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=daniels@collabora.com \
--cc=david.heidelberg@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=emma@anholt.net \
--cc=guilherme.gallo@collabora.com \
--cc=gustavo.padovan@collabora.com \
--cc=helen.koike@collabora.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robdclark@gmail.com \
--cc=sergi.blanch.torne@collabora.com \
--cc=virtualization@lists.linux-foundation.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