All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Cole <elenstev@mesatop.com>
To: Dave Kleikamp <shaggy@austin.ibm.com>
Cc: Dave Olien <dmo@osdl.org>,
	Linus Torvalds <torvalds@transmeta.com>,
	linux-kernel@vger.kernel.org
Subject: [PATCH] 2.5-bk K&R to ANSI conversions for fs/jfs/jfs_dmap.c and jfs_xtree.c
Date: 10 Jun 2003 19:32:44 -0600	[thread overview]
Message-ID: <1055295164.1983.25.camel@spc> (raw)

This patch removes the first of the following warnings when doing
make C=1 bzImage with the sparse checker cleverly installed as
/usr/local/bin/sparse.

  CHECK   fs/jfs/jfs_dmap.c
warning: fs/jfs/jfs_dmap.c:3053:14: non-ANSI parameter list
warning: fs/jfs/jfs_dmap.c:1315:10: not addressable
warning: fs/jfs/jfs_dmap.c:1792:8: not addressable
warning: fs/jfs/jfs_dmap.c:3441:10: not addressable
  CC      fs/jfs/jfs_dmap.o

No "non-ANSI parameter list" warnings for fs/jfs/jfs_xtree.c were
received, presumably because _JFS_WIP wasn't defined.  This patch
converts the xtGather function declaration anyway.

Steven


diff -ur bk-current/fs/jfs/jfs_dmap.c linux/fs/jfs/jfs_dmap.c
--- bk-current/fs/jfs/jfs_dmap.c	2003-06-09 18:36:51.000000000 -0600
+++ linux/fs/jfs/jfs_dmap.c	2003-06-09 22:02:27.000000000 -0600
@@ -3050,7 +3050,7 @@
  * RETURN VALUES:
  *      none
  */
-void fsDirty()
+void fsDirty(void)
 {
 	printk("fsDirty(): bye-bye\n");
 	assert(0);
diff -ur bk-current/fs/jfs/jfs_xtree.c linux/fs/jfs/jfs_xtree.c
--- bk-current/fs/jfs/jfs_xtree.c	2003-06-09 18:34:10.000000000 -0600
+++ linux/fs/jfs/jfs_xtree.c	2003-06-09 22:02:50.000000000 -0600
@@ -4225,8 +4225,7 @@
  *      at the current entry at the current subtree root page
  *
  */
-int xtGather(t)
-btree_t *t;
+int xtGather(btree_t *t)
 {
 	int rc = 0;
 	xtpage_t *p;






                 reply	other threads:[~2003-06-11  1:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1055295164.1983.25.camel@spc \
    --to=elenstev@mesatop.com \
    --cc=dmo@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shaggy@austin.ibm.com \
    --cc=torvalds@transmeta.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.