All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Mahoney <jeffm@suse.com>
To: Chris Mason <chris.mason@oracle.com>
Cc: Shen Feng <shen@cn.fujitsu.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs-progs: update btrfs-debug-tree
Date: Fri, 20 Feb 2009 11:24:04 -0500	[thread overview]
Message-ID: <499ED924.2090705@suse.com> (raw)
In-Reply-To: <1235140108.13249.0.camel@think.oraclecorp.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Chris Mason wrote:
> On Thu, 2009-02-19 at 19:39 -0500, Jeff Mahoney wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Shen Feng wrote:
>>> output objectid in btrfs_disk_key with human readable strings.
>>> Other updates are included for more readable output.
>> This gets messy fast. I'd like to see some sort of generic extensible
>> printk mechanism in the kernel. 
> 
> This is a btrfs-progs patch ;)

Heh, oops. That's an important bit of information.

>> Maybe I've been spoiled by the reiserfs
>> type printing but it seems a lot nicer to do eprintk(&ops, "key: %k\n");
>> than to split them out into different printks. Since the core behavior
>> ends up in vsnprintf, you get it for things like panic for free too.
>> Ideally, the tprintk(&ops, ...) would be hidden behind a btrfs_warning()
>> or something.
>>
>> I have a patch set that implements an extensible printk so that every
>> single pointer type doesn't need to be added to lib/vsprintf.c's pointer().
>>
> 
> That would be interesting, I do miss the old reiserfs %k

Let me clean them up a bit and send to LKML. I can probably do that
later today. I decided to rename it to eprintk from a pretty ugly
printk_custom.

- -Jeff

- --
Jeff Mahoney
SUSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iEYEARECAAYFAkme2SMACgkQLPWxlyuTD7ITSwCeO3XaNGY29kA/5oBcdDL7DqpH
B5wAnRv7RYjzX5h4pX+FbjTGTBGAFy7S
=a5iu
-----END PGP SIGNATURE-----

  reply	other threads:[~2009-02-20 16:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-19  7:06 [PATCH] Btrfs-progs: update btrfs-debug-tree Shen Feng
2009-02-20  0:39 ` Jeff Mahoney
2009-02-20 14:28   ` Chris Mason
2009-02-20 16:24     ` Jeff Mahoney [this message]
2009-02-20 22:26     ` [PATCH] Extensible printk format strings Jeff Mahoney

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=499ED924.2090705@suse.com \
    --to=jeffm@suse.com \
    --cc=chris.mason@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=shen@cn.fujitsu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.