From: Peter Oberparleiter <oberpar@linux.ibm.com>
To: gengcixi@gmail.com, gregkh@linuxfoundation.org,
jirislaby@kernel.org, linux-serial@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: orsonzhai@gmail.com, zhang.lyra@gmail.com,
Cixi Geng <cixi.geng1@unisoc.com>
Subject: Re: [PATCH V8] GCOV: Add config to check the preqequisites situation
Date: Fri, 30 Oct 2020 11:25:24 +0100 [thread overview]
Message-ID: <fb2bbd79-e17a-775e-6f2b-d97acd69b50f@linux.ibm.com> (raw)
In-Reply-To: <20201028131505.482037-1-gengcixi@gmail.com>
On 28.10.2020 14:15, gengcixi@gmail.com wrote:
> From: Cixi Geng <cixi.geng1@unisoc.com>
>
> Introduce new configuration option GCOV_PROFILE_PREREQS that can be
> used to check whether the prerequisites for enabling gcov profiling
> for specific files and directories are met.
>
> Only add SERIAL_GCOV for an example.
[...]
> +config GCOV_PROFILE_PREREQS
> + bool "Profile Kernel for prereqs"
> + def_bool y if GCOV_KERNEL && !COMPILE_TEST
> + help
> + This options activates profiling for the specified kernel modules.
> + When some modules need Gcov data, enable this config, then configure
> + with gcov on the corresponding modules,The directories or files of
> + these modules will be added profiling flags after kernel compile.
> +
> endmenu
This version still produces a prompt during make oldconfig. You need to
remove the "bool" line and the "help" lines.
Before sending another version please test it to make sure that it does
not produce a prompt.
--
Peter Oberparleiter
Linux on Z Development - IBM Germany
prev parent reply other threads:[~2020-10-30 10:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-28 13:15 [PATCH V8] GCOV: Add config to check the preqequisites situation gengcixi
2020-10-30 10:25 ` Peter Oberparleiter [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=fb2bbd79-e17a-775e-6f2b-d97acd69b50f@linux.ibm.com \
--to=oberpar@linux.ibm.com \
--cc=cixi.geng1@unisoc.com \
--cc=gengcixi@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=orsonzhai@gmail.com \
--cc=zhang.lyra@gmail.com \
/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).