All of lore.kernel.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Joe Perches <joe@perches.com>
Cc: linux-mtd@lists.infradead.org,
	David Woodhouse <dwmw2@infradead.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] jffs2: logging message neatening
Date: Wed, 29 Feb 2012 14:08:10 +0200	[thread overview]
Message-ID: <1330517290.3545.107.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <cover.1329349881.git.joe@perches.com>

[-- Attachment #1: Type: text/plain, Size: 3771 bytes --]

On Wed, 2012-02-15 at 15:56 -0800, Joe Perches wrote:
> Joe Perches (4):
>   jffs2: Convert most D1/D2 macros to jffs2_dbg
>   jffs2: Convert printks to pr_<level>
>   jffs2: Use pr_fmt and remove jffs: from formats
>   jffs2: Standardize JFFS_<LEVEL> uses

Thanks for the work, appreciated. But your patch introduces new sparse
and smatch warnings, which did not exist before your patch:

Successfully built configuration "l2_mxs_defconfig,arm,arm-unknown-linux-gnueabi-", results:

--- before_patching.log
+++ after_patching.log 
@@ @@
+fs/jffs2/file.c:330:2: warning: signed and unsigned type in conditional expression [-Wsign-compare]
@@ @@
-fs/jffs2/read.c:154 jffs2_read_dnode(129) warn: possible memory leak of 'decomprbuf' [smatch]
-fs/jffs2/read.c:154 jffs2_read_dnode(129) warn: possible memory leak of 'readbuf' [smatch]
+fs/jffs2/read.c:154 jffs2_read_dnode(131) warn: possible memory leak of 'decomprbuf' [smatch]
+fs/jffs2/read.c:154 jffs2_read_dnode(131) warn: possible memory leak of 'readbuf' [smatch]
@@ @@
-fs/jffs2/scan.c:108:54: warning: suggest braces around empty body in an 'if' statement [-Wempty-body]
@@ @@
+fs/jffs2/super.c:377:1: error: directive in argument list [sparse]
+fs/jffs2/super.c:379:1: error: directive in argument list [sparse]
+fs/jffs2/super.c:380:1: error: directive in argument list [sparse]
+fs/jffs2/super.c:382:1: error: directive in argument list [sparse]

Would you please take a look? Ideally patches should eliminate warnings,
not introduce new ones.

Also, your patch does not apply cleanly to my l2-mtd tree - and this is
the tree which is currently used for merging MTD and JFFS2 stuff
upstream, and it is in linux-next as well. Would you send patches
against the l2 tree?

Also, there are several checkpatch.pl complaints, please, take a look:

--------------------------------------------------------------------------------

checkpatch.pl has some complaints:

--------------------------------------------------------------------------------

checkpatch.pl results for patch "[PATCH 2/4] jffs2: Convert printks to pr_<level>"

WARNING:LONG_LINE: line over 80 characters
#893: FILE: fs/jffs2/nodemgmt.c:269:
+                               list_empty(&c->erase_pending_list) ? "yes" : "no");

WARNING:LONG_LINE: line over 80 characters
#1094: FILE: fs/jffs2/scan.c:31:
+                       pr_notice("Further such events for this erase block will not be printed\n"); \

total: 0 errors, 2 warnings, 1523 lines checked

--------------------------------------------------------------------------------

checkpatch.pl results for patch "[PATCH 3/4] jffs2: Use pr_fmt and remove jffs: from formats"

WARNING:LONG_LINE: line over 80 characters
#102: FILE: fs/jffs2/build.c:312:
+       dbg_fsbuild("trigger levels (size %d KiB, block size %d KiB, %d blocks)\n",

total: 0 errors, 1 warnings, 432 lines checked

--------------------------------------------------------------------------------

checkpatch.pl results for the entire squashed patch-set

WARNING:LONG_LINE: line over 80 characters
#3480: FILE: fs/jffs2/nodemgmt.c:269:
+                               list_empty(&c->erase_pending_list) ? "yes" : "no");

WARNING:LONG_LINE: line over 80 characters
#3681: FILE: fs/jffs2/scan.c:31:
+                       pr_notice("Further such events for this erase block will not be printed\n"); \

WARNING:LONG_LINE: line over 80 characters
#4448: FILE: fs/jffs2/build.c:312:
+       dbg_fsbuild("trigger levels (size %d KiB, block size %d KiB, %d blocks)\n",

total: 0 errors, 3 warnings, 4324 lines checked

--------------------------------------------------------------------------------

-- 
Best Regards,
Artem Bityutskiy

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Joe Perches <joe@perches.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
	linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] jffs2: logging message neatening
Date: Wed, 29 Feb 2012 14:08:10 +0200	[thread overview]
Message-ID: <1330517290.3545.107.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <cover.1329349881.git.joe@perches.com>

[-- Attachment #1: Type: text/plain, Size: 3771 bytes --]

On Wed, 2012-02-15 at 15:56 -0800, Joe Perches wrote:
> Joe Perches (4):
>   jffs2: Convert most D1/D2 macros to jffs2_dbg
>   jffs2: Convert printks to pr_<level>
>   jffs2: Use pr_fmt and remove jffs: from formats
>   jffs2: Standardize JFFS_<LEVEL> uses

Thanks for the work, appreciated. But your patch introduces new sparse
and smatch warnings, which did not exist before your patch:

Successfully built configuration "l2_mxs_defconfig,arm,arm-unknown-linux-gnueabi-", results:

--- before_patching.log
+++ after_patching.log 
@@ @@
+fs/jffs2/file.c:330:2: warning: signed and unsigned type in conditional expression [-Wsign-compare]
@@ @@
-fs/jffs2/read.c:154 jffs2_read_dnode(129) warn: possible memory leak of 'decomprbuf' [smatch]
-fs/jffs2/read.c:154 jffs2_read_dnode(129) warn: possible memory leak of 'readbuf' [smatch]
+fs/jffs2/read.c:154 jffs2_read_dnode(131) warn: possible memory leak of 'decomprbuf' [smatch]
+fs/jffs2/read.c:154 jffs2_read_dnode(131) warn: possible memory leak of 'readbuf' [smatch]
@@ @@
-fs/jffs2/scan.c:108:54: warning: suggest braces around empty body in an 'if' statement [-Wempty-body]
@@ @@
+fs/jffs2/super.c:377:1: error: directive in argument list [sparse]
+fs/jffs2/super.c:379:1: error: directive in argument list [sparse]
+fs/jffs2/super.c:380:1: error: directive in argument list [sparse]
+fs/jffs2/super.c:382:1: error: directive in argument list [sparse]

Would you please take a look? Ideally patches should eliminate warnings,
not introduce new ones.

Also, your patch does not apply cleanly to my l2-mtd tree - and this is
the tree which is currently used for merging MTD and JFFS2 stuff
upstream, and it is in linux-next as well. Would you send patches
against the l2 tree?

Also, there are several checkpatch.pl complaints, please, take a look:

--------------------------------------------------------------------------------

checkpatch.pl has some complaints:

--------------------------------------------------------------------------------

checkpatch.pl results for patch "[PATCH 2/4] jffs2: Convert printks to pr_<level>"

WARNING:LONG_LINE: line over 80 characters
#893: FILE: fs/jffs2/nodemgmt.c:269:
+                               list_empty(&c->erase_pending_list) ? "yes" : "no");

WARNING:LONG_LINE: line over 80 characters
#1094: FILE: fs/jffs2/scan.c:31:
+                       pr_notice("Further such events for this erase block will not be printed\n"); \

total: 0 errors, 2 warnings, 1523 lines checked

--------------------------------------------------------------------------------

checkpatch.pl results for patch "[PATCH 3/4] jffs2: Use pr_fmt and remove jffs: from formats"

WARNING:LONG_LINE: line over 80 characters
#102: FILE: fs/jffs2/build.c:312:
+       dbg_fsbuild("trigger levels (size %d KiB, block size %d KiB, %d blocks)\n",

total: 0 errors, 1 warnings, 432 lines checked

--------------------------------------------------------------------------------

checkpatch.pl results for the entire squashed patch-set

WARNING:LONG_LINE: line over 80 characters
#3480: FILE: fs/jffs2/nodemgmt.c:269:
+                               list_empty(&c->erase_pending_list) ? "yes" : "no");

WARNING:LONG_LINE: line over 80 characters
#3681: FILE: fs/jffs2/scan.c:31:
+                       pr_notice("Further such events for this erase block will not be printed\n"); \

WARNING:LONG_LINE: line over 80 characters
#4448: FILE: fs/jffs2/build.c:312:
+       dbg_fsbuild("trigger levels (size %d KiB, block size %d KiB, %d blocks)\n",

total: 0 errors, 3 warnings, 4324 lines checked

--------------------------------------------------------------------------------

-- 
Best Regards,
Artem Bityutskiy

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2012-02-29 12:05 UTC|newest]

Thread overview: 39+ 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:30     ` Artem Bityutskiy
2012-03-05 16:56     ` Joe Perches
2012-03-05 16:56       ` Joe Perches
2012-03-09 11:53       ` Artem Bityutskiy
2012-03-09 11:53         ` Artem Bityutskiy
2012-03-09 18:49         ` Joe Perches
2012-03-09 18:49           ` Joe Perches
2012-03-12 13:12           ` Artem Bityutskiy
2012-03-12 13:12             ` Artem Bityutskiy
2012-03-12 15:33             ` Joe Perches
2012-03-12 15:33               ` Joe Perches
2012-03-12 16:35               ` Artem Bityutskiy
2012-03-12 16:35                 ` Artem Bityutskiy
2012-03-12 17:11                 ` Joe Perches
2012-03-12 17:11                   ` Joe Perches
2012-03-13 12:39                   ` Artem Bityutskiy
2012-03-13 12:39                     ` Artem Bityutskiy
2012-03-13 16:34                     ` Joe Perches
2012-03-13 16:34                       ` Joe Perches
2012-03-14 10:54                       ` Artem Bityutskiy
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-09 21:59           ` Joe Perches
2012-03-12 13:50           ` Artem Bityutskiy
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 ` Artem Bityutskiy [this message]
2012-02-29 12:08   ` [PATCH 0/4] jffs2: logging message neatening Artem Bityutskiy
2012-02-29 12:12   ` Artem Bityutskiy
2012-02-29 12:12     ` Artem Bityutskiy
2012-02-29 19:02   ` Joe Perches
2012-02-29 19:02     ` Joe Perches
2012-03-01  7:36     ` Artem Bityutskiy
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=1330517290.3545.107.camel@sauron.fi.intel.com \
    --to=dedekind1@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=joe@perches.com \
    --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 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.