From: Li Zhijian <lizhijian@cn.fujitsu.com>
To: <shuah@kernel.org>, <linux-kselftest@vger.kernel.org>
Cc: <philip.li@intel.com>, <linux-kernel@vger.kernel.org>,
Li Zhijian <lizhijian@cn.fujitsu.com>,
kernel test robot <lkp@intel.com>
Subject: [PATCH v3 1/2] selftests/sync: Remove the deprecated config SYNC
Date: Tue, 31 Aug 2021 18:23:15 +0800 [thread overview]
Message-ID: <20210831102316.280512-2-lizhijian@cn.fujitsu.com> (raw)
In-Reply-To: <20210831102316.280512-1-lizhijian@cn.fujitsu.com>
SYNC was removed since
aff9da10e21 ("staging/android: make sync_timeline internal to sw_sync")
LKP/0Day will check if all configs listing under selftests are able to
be enabled properly.
For the missing configs, it will report something like:
LKP WARN miss config CONFIG_SYNC= of sync/config
- it's not reasonable to keep the deprecated configs.
- configs under kselftests are recommended by corresponding tests.
So if some configs are missing, it will impact the testing results
CC: Philip Li <philip.li@intel.com>
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: Li Zhijian <lizhijian@cn.fujitsu.com>
---
V3: update commit logs # Shuah
---
tools/testing/selftests/sync/config | 1 -
1 file changed, 1 deletion(-)
diff --git a/tools/testing/selftests/sync/config b/tools/testing/selftests/sync/config
index 1ab7e8130db2..47ff5afc3727 100644
--- a/tools/testing/selftests/sync/config
+++ b/tools/testing/selftests/sync/config
@@ -1,4 +1,3 @@
CONFIG_STAGING=y
CONFIG_ANDROID=y
-CONFIG_SYNC=y
CONFIG_SW_SYNC=y
--
2.31.1
next prev parent reply other threads:[~2021-08-31 10:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-31 10:23 [PATCH v3 0/2] kselftests: clean configs Li Zhijian
2021-08-31 10:23 ` Li Zhijian [this message]
2021-08-31 10:23 ` [PATCH v3 2/2] selftests/cpufreq: Rename DEBUG_PI_LIST to DEBUG_PLIST Li Zhijian
2021-08-31 12:05 ` Viresh Kumar
2021-08-31 16:50 ` [PATCH v3 0/2] kselftests: clean configs Shuah Khan
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=20210831102316.280512-2-lizhijian@cn.fujitsu.com \
--to=lizhijian@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lkp@intel.com \
--cc=philip.li@intel.com \
--cc=shuah@kernel.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;
as well as URLs for NNTP newsgroup(s).