From: Joe Lawrence <joe.lawrence@redhat.com>
To: Anders Roxell <anders.roxell@linaro.org>,
shuah@kernel.org, pmladek@suse.com, mbenes@suse.cz,
jikos@kernel.org, jpoimboe@redhat.com
Cc: live-patching@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selftests: livepatch: add missing fragments to config
Date: Wed, 14 Aug 2019 09:20:49 -0400 [thread overview]
Message-ID: <e01a1182-d9cf-b2c2-78a9-35f60861e4a9@redhat.com> (raw)
In-Reply-To: <20190814111651.28433-1-anders.roxell@linaro.org>
On 8/14/19 7:16 AM, Anders Roxell wrote:
> When generating config with 'make defconfig kselftest-merge' fragment
> CONFIG_TEST_LIVEPATCH=m isn't set.
>
> Rework to enable CONFIG_LIVEPATCH and CONFIG_DYNAMIC_DEBUG as well.
>
> Signed-off-by: Anders Roxell <anders.roxell@linaro.org>
> ---
> tools/testing/selftests/livepatch/config | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/tools/testing/selftests/livepatch/config b/tools/testing/selftests/livepatch/config
> index 0dd7700464a8..ad23100cb27c 100644
> --- a/tools/testing/selftests/livepatch/config
> +++ b/tools/testing/selftests/livepatch/config
> @@ -1 +1,3 @@
> +CONFIG_LIVEPATCH=y
> +CONFIG_DYNAMIC_DEBUG=y
> CONFIG_TEST_LIVEPATCH=m
>
Cool, I didn't know about that make target when doing commit
bae054372aba ("selftests/livepatch: add DYNAMIC_DEBUG config dependency")
How does kselftest-merge verify dependencies?
CONFIG_LIVEPATCH has its own list of configuration dependencies (see
kernel/livepatch/Kconfig) but we don't list all of those in this config
file. Just curious.
Thanks,
-- Joe
prev parent reply other threads:[~2019-08-14 13:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-14 11:16 [PATCH] selftests: livepatch: add missing fragments to config Anders Roxell
2019-08-14 13:20 ` Joe Lawrence [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=e01a1182-d9cf-b2c2-78a9-35f60861e4a9@redhat.com \
--to=joe.lawrence@redhat.com \
--cc=anders.roxell@linaro.org \
--cc=jikos@kernel.org \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=pmladek@suse.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).