From: Jason Baron <jbaron@redhat.com>
To: jim.cromie@gmail.com
Cc: rusty@rustcorp.com.au, linux-kernel@vger.kernel.org
Subject: Re: [00/11] pr_debug during module initialization
Date: Fri, 23 Mar 2012 16:27:13 -0400 [thread overview]
Message-ID: <20120323202713.GA6039@redhat.com> (raw)
In-Reply-To: <1331766126-11674-1-git-send-email-jim.cromie@gmail.com>
On Wed, Mar 14, 2012 at 05:01:55PM -0600, jim.cromie@gmail.com wrote:
> This is 3rd revision of the dyndbg modinit patches, previously sent
> Dec 11. Patches 1-17/25 sent then were added to driver-core-next,
> this set reworks the remainder.
>
> It implements the "fake" module param approach proposed by
> Thomas Renninger, back in https://lkml.org/lkml/2010/9/15/397
>
Hi,
I'm wondering, if we leave the cmdline parameter: 'ddebug_query=' around
for a bit before removing it, so it doesn't get dropped too suddenly.
Perhaps, we add a warning msg, for people that are still using it
for a few releases warning that it is deprecated, before dropping it.
Also, let's add the 'dyndbg=' syntax to Documentation/kernel-parameters.txt.
A previous version had a build-time error if a module used 'dyndbg' as a
module param - why did that get dropped?
Thanks!
-Jason
next prev parent reply other threads:[~2012-03-23 20:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-14 23:01 [00/11] pr_debug during module initialization jim.cromie
2012-03-14 23:01 ` [PATCH 01/11] init: trivial tweaks to initcall_levels jim.cromie
2012-03-14 23:01 ` [PATCH 02/11] dynamic_debug: fix leading spaces jim.cromie
2012-03-14 23:01 ` [PATCH 03/11] dynamic_debug: replace if (verbose) pr_info with macro vpr_info jim.cromie
2012-03-14 23:01 ` [PATCH 04/11] dynamic_debug: change ddebug_query core param to dyndbg jim.cromie
2012-03-14 23:02 ` [PATCH 05/11] params: add param-name to parse_one's pr_debug() jim.cromie
2012-03-14 23:02 ` [PATCH 06/11] params: add 3rd arg to option handler callback signature jim.cromie
2012-03-14 23:02 ` [PATCH 07/11] dynamic_debug: make dynamic-debug work during module initialization jim.cromie
2012-03-14 23:02 ` [PATCH 08/11] pnp: if CONFIG_DYNAMIC_DEBUG, use pnp.dyndbg instead of pnp.debug jim.cromie
2012-03-14 23:02 ` [PATCH 09/11] dynamic_debug: add modname arg to exec_query callchain jim.cromie
2012-03-14 23:02 ` [PATCH 10/11] dynamic_debug: update Documentation/*, Kconfig.debug jim.cromie
2012-03-14 23:02 ` [PATCH 11/11] dynamic_debug: init with core_initcall, not arch_initcall jim.cromie
2012-03-19 2:04 ` [00/11] pr_debug during module initialization Rusty Russell
2012-03-19 6:17 ` Jim Cromie
2012-03-19 23:27 ` Rusty Russell
2012-03-23 20:27 ` Jason Baron [this message]
2012-03-24 0:12 ` Jim Cromie
2012-03-26 0:24 ` Rusty Russell
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=20120323202713.GA6039@redhat.com \
--to=jbaron@redhat.com \
--cc=jim.cromie@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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