mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@fs.tum.de>
To: Joerg Reuter DL1BKE <jreuter@yaina.de>
Cc: linux-net@vger.kernel.org, jgarzik@pobox.com,
	linux-kernel@vger.kernel.org
Subject: [2.6 patch] fix bpqether.c compile without CONFIG_PROC_FS
Date: Wed, 27 Aug 2003 09:12:15 +0200	[thread overview]
Message-ID: <20030827071215.GL7038@fs.tum.de> (raw)

I got the following compile error when trying to compile 2.6.0-test4-mm1 
without CONFIG_PROC_FS (but this problem is most likely not limited to 
-mm):

<--  snip  -->

...
  CC      drivers/net/hamradio/bpqether.o
drivers/net/hamradio/bpqether.c: In function `bpq_init_driver':
drivers/net/hamradio/bpqether.c:608: parse error before `do'
...
make[3]: *** [drivers/net/hamradio/bpqether.o] Error 1

<--  snip  -->


It seems something like the following patch is needed:


--- linux-2.6.0-test4-mm1/drivers/net/hamradio/bpqether.c~	2003-08-23 01:55:31.000000000 +0200
+++ linux-2.6.0-test4-mm1/drivers/net/hamradio/bpqether.c	2003-08-27 09:00:04.000000000 +0200
@@ -605,6 +605,7 @@
 
 	printk(banner);
 
+#ifdef CONFIG_PROC_FS
 	if (!proc_net_fops_create("bpqether", S_IRUGO, &bpq_info_fops)) {
 		printk(KERN_ERR
 			"bpq: cannot create /proc/net/bpqether entry.\n");
@@ -612,6 +613,7 @@
 		dev_remove_pack(&bpq_packet_type);
 		return -ENOENT;
 	}
+#endif  /* CONFIG_PROC_FS */
 
 	rtnl_lock();
 	for (dev = dev_base; dev != NULL; dev = dev->next) {



cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


             reply	other threads:[~2003-08-27  7:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-27  7:12 Adrian Bunk [this message]
2003-08-28  6:42 ` David S. Miller

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=20030827071215.GL7038@fs.tum.de \
    --to=bunk@fs.tum.de \
    --cc=jgarzik@pobox.com \
    --cc=jreuter@yaina.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@vger.kernel.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

Powered by JetHome