mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Anton Altaparmakov <anton@tuxera.com>
Cc: Fabian Frederick <fabf@skynet.be>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	akpm <akpm@linux-foundation.org>
Subject: Re: [PATCH 1/1] NTFS: Logging clean-up
Date: Sun, 16 Mar 2014 09:42:43 -0700	[thread overview]
Message-ID: <1394988163.5689.29.camel@joe-AO722> (raw)
In-Reply-To: <DB070619-215B-407E-827E-B9F383465DE2@tuxera.com>

On Sun, 2014-03-16 at 16:27 +0000, Anton Altaparmakov wrote:
> Hi,

Hello all.

> On 16 Mar 2014, at 16:12, Joe Perches <joe@perches.com> wrote:

> > This changes prefixes from "NTFS-fs" to "ntfs"
> > and should be at a minimum mentioned in the
> > changelog.
> 
> As long as it says ntfs in the string so dmesg output can be
> "grep -i ntfs"-ed I am not fussed.

Nor I really, but mentioning what output changes occur
in the changelog is helpful.

> > Converting printk(KERN_DEBUG -> pr_debug will
> > not always emit that message now.  Now, only if
> > DEBUG is #defined or dynamic_debugging is enabled
> > for the build _and_ the message is specifically
> > enabled will the message be output.
> > 
> > So, the debugging output has been silenced by default.
> > 
> > That's not necessarily good.
> 
> No that is not good at all.  I didn't know about those pr_debug
> semantics so thank you for pointing them out.  That needs fixing
> otherwise we might as well not have the messages at all...  Being able
> to enable all ntfs debug messages using a insmod option or via /proc
> as is at the moment is a very valuable debugging too and I have
> scripts that use this so am not keen on this being changed at all.

> Fabian, can you please fix the issues pointed out by Joe and also
> please make sure you actually test it!

I think a good way to enable these by default is to add
#define DEBUG before any other #include (or any include
that includes printk.h actually), but there may be other
sections of code that are #ifdef DEBUG that would need
inspecting to make sure that more code isn't compiled in
than before.

cheers, Joe



  reply	other threads:[~2014-03-16 16:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-16 12:27 Fabian Frederick
2014-03-16 15:53 ` Anton Altaparmakov
2014-03-16 16:12   ` Joe Perches
2014-03-16 16:27     ` Anton Altaparmakov
2014-03-16 16:42       ` Joe Perches [this message]
2014-03-16 18:42       ` Fabian Frederick

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=1394988163.5689.29.camel@joe-AO722 \
    --to=joe@perches.com \
    --cc=akpm@linux-foundation.org \
    --cc=anton@tuxera.com \
    --cc=fabf@skynet.be \
    --cc=linux-kernel@vger.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

all inboxes | Powered by JetHome®