public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Baron <jbaron@redhat.com>
To: Greg KH <greg@kroah.com>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
	linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	joe@perches.com, nick@nick-andrew.net
Subject: Re: [PATCH 1/7] dynamic debug v2 - infrastructure
Date: Thu, 14 Aug 2008 17:05:22 -0400	[thread overview]
Message-ID: <20080814210512.GA6087@redhat.com> (raw)
In-Reply-To: <20080814145348.GA25422@kroah.com>

On Thu, Aug 14, 2008 at 07:53:48AM -0700, Greg KH wrote:
> Also, would it make sense to add a patch like the one below to this
> code?  It might be nice to know when each module's debugging value is
> manually changed by the user for the log files.
> 
> If you like it, I can merge it in the main patch.
> 
> thanks,
> 
> greg k-h
> 
> ---
>  lib/dynamic_printk.c |    6 ++++++
>  1 file changed, 6 insertions(+)
> 
> --- a/lib/dynamic_printk.c
> +++ b/lib/dynamic_printk.c
> @@ -288,6 +288,9 @@ static ssize_t pr_debug_write(struct fil
>  					num_enabled++;
>  					dynamic_enabled = DYNAMIC_ENABLED_SOME;
>  					err = 0;
> +					printk(KERN_DEBUG
> +					       "debugging enabled for module %s",
> +					       elem->name);
>  				} else if (!value && (elem->enable == 1)) {
>  					elem->enable = 0;
>  					num_enabled--;
> @@ -304,6 +307,9 @@ static ssize_t pr_debug_write(struct fil
>  						dynamic_enabled =
>  							DYNAMIC_ENABLED_NONE;
>  					err = 0;
> +					printk(KERN_DEBUG
> +					       "debugging disabled for module "
> +					       "%s", elem->name);
>  				}
>  			}
>  		}


looks good. we might also want to add a message for the cases where are the
modules are enabled/disabled too.

thanks,

-Jason

  reply	other threads:[~2008-08-14 21:06 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-15 21:31 [PATCH 1/7] dynamic debug v2 - infrastructure Jason Baron
2008-07-17  7:01 ` Greg KH
2008-07-17 21:20   ` Jason Baron
2008-07-17 22:32     ` Greg KH
2008-07-17 22:56       ` Dominik Brodowski
2008-07-17 23:35         ` Greg KH
2008-07-18  6:37           ` Dominik Brodowski
2008-07-18 14:39       ` Jason Baron
2008-08-08 21:51       ` Jason Baron
2008-08-09  1:07         ` Greg KH
2008-08-11 14:12           ` Jason Baron
2008-08-11 16:45             ` Greg KH
2008-08-09  2:38         ` Randy Dunlap
2008-08-11 17:36           ` Jason Baron
2008-08-11 22:33             ` Greg KH
2008-08-12 19:48               ` Jason Baron
2008-08-12 20:09                 ` Greg KH
2008-08-12 20:46                   ` Jason Baron
2008-08-13  1:08                     ` Greg KH
2008-08-13  1:16                       ` Andrew Morton
2008-08-13  3:38                         ` Greg KH
2008-08-13 20:00                           ` Sam Ravnborg
2008-08-13 22:49                             ` jbaron
2008-08-13 23:54                             ` Greg KH
2008-08-14  1:25                               ` Greg KH
2008-08-13 19:05                       ` Jason Baron
2008-08-14 14:53                     ` Greg KH
2008-08-14 21:05                       ` Jason Baron [this message]
2008-09-16  0:03 ` 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=20080814210512.GA6087@redhat.com \
    --to=jbaron@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=greg@kroah.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nick@nick-andrew.net \
    --cc=randy.dunlap@oracle.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