From: Jim Cromie <jim.cromie@gmail.com>
To: jbaron@akamai.com, linux-kernel@vger.kernel.org
Cc: Jim Cromie <jim.cromie@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Changbin Du <changbin.du@intel.com>,
Randy Dunlap <rdunlap@infradead.org>,
Masahiro Yamada <masahiroy@kernel.org>,
Shuah Khan <skhan@linuxfoundation.org>,
Krzysztof Kozlowski <krzk@kernel.org>
Subject: [PATCH 3/7] dyndbg: select ZPOOL in Kconfig.debug
Date: Fri, 7 Aug 2020 14:09:50 -0600 [thread overview]
Message-ID: <20200807200957.1269454-4-jim.cromie@gmail.com> (raw)
In-Reply-To: <20200807200957.1269454-1-jim.cromie@gmail.com>
dyndbg will next need zs_malloc and friends, so add config reqs now,
to avoid touching make-deps late in a patch-set.
I used select in order not to hide dyndbg inadvertently.
I want to say recommends, since it could be an optional feature.
Whats the best way ?
Signed-off-by: Jim Cromie <jim.cromie@gmail.com>
---
lib/Kconfig.debug | 1 +
1 file changed, 1 insertion(+)
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index 9ad9210d70a1..a7973063baf0 100644
--- a/lib/Kconfig.debug
+++ b/lib/Kconfig.debug
@@ -100,6 +100,7 @@ config DYNAMIC_DEBUG
depends on PRINTK
depends on (DEBUG_FS || PROC_FS)
select DYNAMIC_DEBUG_CORE
+ select ZPOOL
help
Compiles debug level messages into the kernel, which would not
--
2.26.2
next prev parent reply other threads:[~2020-08-07 20:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-07 20:09 [PATCH 0/7] dyndbg: WIP diet plan Jim Cromie
2020-08-07 20:09 ` [PATCH 1/7] dyndbg: give %3u width in pr-format, cosmetic only Jim Cromie
2020-08-07 20:09 ` [PATCH 2/7] dyndbg: motivate a diet plan Jim Cromie
2020-08-07 20:09 ` Jim Cromie [this message]
2020-08-09 5:05 ` [PATCH 3/7] dyndbg: select ZPOOL in Kconfig.debug Randy Dunlap
2020-08-09 15:09 ` jim.cromie
2020-08-07 20:09 ` [PATCH 4/7] dyndbg: split struct _ddebug in 2, creating _ddebug_callsite Jim Cromie
2020-08-07 20:09 ` [PATCH 5/7] dyndbg: WIP replace __dyndbg_callsite section with a zs-pool copy Jim Cromie
2020-08-07 23:50 ` kernel test robot
2020-08-07 20:09 ` [PATCH 6/7] dyndbg: add locking around zpool-add loop in zpool-init Jim Cromie
2020-08-07 20:09 ` [PATCH 6/8] dyndbg: ddebug_zpool_remove Jim Cromie
2020-08-07 20:09 ` [PATCH 7/7] dyndbg: enable 'cache' of active pr_debug callsites Jim Cromie
2020-08-09 4:35 ` [dyndbg] 4397a3e7bf: BUG:sleeping_function_called_from_invalid_context_at_mm/slab.h kernel test robot
2020-08-12 15:11 ` jim.cromie
2020-08-07 20:09 ` [PATCH 8/8] dyndbg: add locking around zpool-add loop in zpool-init Jim Cromie
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=20200807200957.1269454-4-jim.cromie@gmail.com \
--to=jim.cromie@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=changbin.du@intel.com \
--cc=jbaron@akamai.com \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.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®