From: Joe Perches <joe@perches.com>
To: dedekind1@gmail.com
Cc: David Woodhouse <dwmw2@infradead.org>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] jffs2: Convert most D1/D2 macros to jffs2_dbg
Date: Mon, 05 Mar 2012 08:56:55 -0800 [thread overview]
Message-ID: <1330966615.3140.6.camel@joe2Laptop> (raw)
In-Reply-To: <1330965033.7220.16.camel@golum>
On Mon, 2012-03-05 at 18:30 +0200, Artem Bityutskiy wrote:
> On Wed, 2012-02-15 at 15:56 -0800, Joe Perches wrote:
[]
> I would just kill all the levels and left only the first one - others
> are not useful. This FS is in the kernel for ages and it is safe to
> assume it is robust enough to require no level 2. And change the Kconfig
> correspondingly.
>
> I would accept that to my l2 tree, although the final word is from
> dwmw2, of course.
Separate patch I think.
> Would it please be possible to make the patch which introduces jffs2_dbg
> macros be separate? It is very difficult to find the definition (most
> interesting in this patch) while looking at the e-mail.
Shrug. Maybe if David W wants it so.
> How about make one more step forward and remove this prefix from all the
> messages and make it to be part of the 'jffs2_dbg' macro?
Maybe in another patch.
[]
> > + jffs2_dbg(1, "%s(): SIGSTOP received\n",
> > + __func__);
jffs2_dbg(1, "%s(): SIGSTOP received\n",
> May become a one-liner here and in many other places.
Goes beyond 80 chars.
> > + jffs2_dbg(1, "%s(): SIGKILL received\n",
> > + __func__);
>
> Ditto, and there are many other places.
Same as above.
> > - D1(printk(KERN_DEBUG "jffs2_erase_block(): erase block %#08x (range %#08x-%#08x)\n",
> > - jeb->offset, jeb->offset, jeb->offset + c->sector_size));
> > + jffs2_dbg(1, "%s(): erase block %#08x (range %#08x-%#08x)\n",
> > + __func__,
> > + jeb->offset, jeb->offset, jeb->offset + c->sector_size);
>
> Probably lines can be joined?
Going to have that many lines anyway.
> > if (jeb == c->gcblock) {
> > - D1(printk(KERN_DEBUG "Expanding down to cover frag (0x%x-0x%x) in gcblock at %08x\n",
> > - frag->ofs, frag->ofs+frag->size, ref_offset(raw)));
> > + jffs2_dbg(1, "Expanding down to cover frag (0x%x-0x%x) in gcblock at %08x\n",
> > + frag->ofs,
> > + frag->ofs + frag->size,
> > + ref_offset(raw));
>
> Lines can be joined, and in other places as well.
Not really. Try it.
> > - frag->ofs, frag->ofs+frag->size, jeb->offset));
> > + jffs2_dbg(1, "Not expanding down to cover frag (0x%x-0x%x) in clean block %08x\n",
> > + frag->ofs,
> > + frag->ofs + frag->size,
> > + jeb->offset);
>
> > - D1(printk(KERN_DEBUG "Obsoleting previously unchecked node at 0x%08x of len %x: ", ref_offset(ref), freed_len));
> > + jffs2_dbg(1, "Obsoleting previously unchecked node at 0x%08x of len %x\n",
> > + ref_offset(ref), freed_len);
>
> What happened to the indentation?
Incorrect before, correct now.
It's still in a D1 block.
next prev parent reply other threads:[~2012-03-05 16:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-15 23:56 [PATCH 0/4] jffs2: logging message neatening Joe Perches
2012-02-15 23:56 ` [PATCH 1/4] jffs2: Convert most D1/D2 macros to jffs2_dbg Joe Perches
2012-03-05 16:30 ` Artem Bityutskiy
2012-03-05 16:56 ` Joe Perches [this message]
2012-03-09 11:53 ` Artem Bityutskiy
2012-03-09 18:49 ` Joe Perches
2012-03-12 13:12 ` Artem Bityutskiy
2012-03-12 15:33 ` Joe Perches
2012-03-12 16:35 ` Artem Bityutskiy
2012-03-12 17:11 ` Joe Perches
2012-03-13 12:39 ` Artem Bityutskiy
2012-03-13 16:34 ` Joe Perches
2012-03-14 10:54 ` Artem Bityutskiy
2012-03-09 21:59 ` [PATCH l2-mtd] jffs2: Fix build when CONFIG_JFFS2_FS_DEBUG > 0 Joe Perches
2012-03-12 13:50 ` Artem Bityutskiy
2012-02-15 23:56 ` [PATCH 2/4] jffs2: Convert printks to pr_<level> Joe Perches
2012-02-15 23:56 ` [PATCH 3/4] jffs2: Use pr_fmt and remove jffs: from formats Joe Perches
2012-02-15 23:56 ` [PATCH 4/4] jffs2: Standardize JFFS_<LEVEL> uses Joe Perches
2012-02-29 12:08 ` [PATCH 0/4] jffs2: logging message neatening Artem Bityutskiy
2012-02-29 12:12 ` Artem Bityutskiy
2012-02-29 19:02 ` Joe Perches
2012-03-01 7:36 ` Artem Bityutskiy
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=1330966615.3140.6.camel@joe2Laptop \
--to=joe@perches.com \
--cc=dedekind1@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).