linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Olaf Dietsche <olaf.dietsche--list.linux-kernel@exmail.de>
To: viro@math.psu.edu
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] 2.5.38 fs/partitions/check.c
Date: Wed, 25 Sep 2002 17:32:00 +0200	[thread overview]
Message-ID: <878z1qjdan.fsf@goat.bogus.local> (raw)

Hi,

when building 2.5.38, I get the following error:

  gcc -Wp,-MD,./.check.o.d -D__KERNEL__ -I/usr/src/kernel/v2.5.38/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i686 -I/usr/src/kernel/v2.5.38/arch/i386/mach-generic -nostdinc -iwithprefix include    -DKBUILD_BASENAME=check   -c -o check.o check.c
check.c: In function `devfs_create_cdrom':
check.c:365: `devfs_handle' undeclared (first use in this function)
check.c:365: (Each undeclared identifier is reported only once
check.c:365: for each function it appears in.)

I don't know, wether this patch is correct, but at least it lets me
compile and run UML 2.5.38

Regards, Olaf.

diff -urN a/fs/partitions/check.c b/fs/partitions/check.c
--- a/fs/partitions/check.c	Wed Sep 25 15:52:01 2002
+++ b/fs/partitions/check.c	Wed Sep 25 16:19:41 2002
@@ -288,6 +288,7 @@
 static struct unique_numspace disc_numspace = UNIQUE_NUMBERSPACE_INITIALISER;
 static devfs_handle_t cdroms;
 static struct unique_numspace cdrom_numspace = UNIQUE_NUMBERSPACE_INITIALISER;
+static devfs_handle_t devfs_handle;
 #endif
 
 static void devfs_create_partitions(struct gendisk *dev)
@@ -297,7 +298,6 @@
 	devfs_handle_t dir, slave;
 	unsigned int devfs_flags = DEVFS_FL_DEFAULT;
 	char dirname[64], symlink[16];
-	static devfs_handle_t devfs_handle;
 	int part, max_p = 1<<dev->minor_shift;
 	struct hd_struct *p = dev->part;
 

                 reply	other threads:[~2002-09-25 15:27 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=878z1qjdan.fsf@goat.bogus.local \
    --to=olaf.dietsche--list.linux-kernel@exmail.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@math.psu.edu \
    /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).