From: Vignesh Raman <vignesh.raman@collabora.com>
To: dri-devel@lists.freedesktop.org
Cc: helen.koike@collabora.com, guilherme.gallo@collabora.com,
sergi.blanch.torne@collabora.com, david.heidelberg@collabora.com,
daniels@collabora.com, gustavo.padovan@collabora.com,
emma@anholt.net, robclark@freedesktop.org, robdclark@google.com,
anholt@google.com, robdclark@gmail.com, airlied@gmail.com,
daniel@ffwll.ch, jani.nikula@linux.intel.com, mripard@kernel.org,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
virtualization@lists.linux-foundation.org,
linux-arm-msm@vger.kernel.org
Subject: [PATCH v2 7/7] drm: ci: Use scripts/config to enable/disable configs
Date: Mon, 4 Sep 2023 21:45:16 +0530 [thread overview]
Message-ID: <20230904161516.66751-8-vignesh.raman@collabora.com> (raw)
In-Reply-To: <20230904161516.66751-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.
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
---
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 92ffd98cd09e..c95f4daac221 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
prev parent reply other threads:[~2023-09-04 16:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 16:15 [PATCH v2 0/7] drm: ci: fixes Vignesh Raman
2023-09-04 16:15 ` [PATCH v2 1/7] drm: ci: igt_runner: remove todo Vignesh Raman
2023-09-04 16:15 ` [PATCH v2 2/7] drm: ci: Force db410c to host mode Vignesh Raman
2023-09-04 16:59 ` Dmitry Baryshkov
2023-09-05 8:43 ` Maxime Ripard
2023-09-05 10:09 ` Vignesh Raman
2023-09-05 11:00 ` Maxime Ripard
2023-09-05 11:10 ` Dmitry Baryshkov
2023-09-05 11:41 ` Vignesh Raman
2023-09-05 11:57 ` Maxime Ripard
2023-09-05 13:36 ` Vignesh Raman
2023-09-05 13:40 ` Maxime Ripard
2023-09-06 5:11 ` Vignesh Raman
2023-09-06 12:55 ` Helen Koike
2023-09-06 13:13 ` Maxime Ripard
2023-09-04 16:15 ` [PATCH v2 3/7] drm: ci: virtio: update ci variables Vignesh Raman
2023-09-04 16:15 ` [PATCH v2 4/7] drm: ci: Enable configs to fix mt8173 boot hang issue Vignesh Raman
2023-09-04 16:15 ` [PATCH v2 5/7] drm: ci: Update xfails Vignesh Raman
2023-09-04 16:15 ` [PATCH v2 6/7] drm: ci: Enable new jobs Vignesh Raman
2023-09-04 16:15 ` Vignesh Raman [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=20230904161516.66751-8-vignesh.raman@collabora.com \
--to=vignesh.raman@collabora.com \
--cc=airlied@gmail.com \
--cc=anholt@google.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=jani.nikula@linux.intel.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=mripard@kernel.org \
--cc=robclark@freedesktop.org \
--cc=robdclark@gmail.com \
--cc=robdclark@google.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
all inboxes | Powered by JetHome®