public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: torvalds@transmeta.com, Adrian Bunk <bunk@fs.tum.de>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Remaining occurances of DEVFS_FL_AUTO_DEVNUM in 2.5.65
Date: Tue, 18 Mar 2003 17:04:09 +0100	[thread overview]
Message-ID: <20030318170409.A7043@lst.de> (raw)
In-Reply-To: <20030318164037.A6878@lst.de>; from hch@lst.de on Tue, Mar 18, 2003 at 04:40:37PM +0100

On Tue, Mar 18, 2003 at 04:40:37PM +0100, Christoph Hellwig wrote:
> > drivers/media/dvb/dvb-core/dvbdev.c:    #define DVB_DEVFS_FLAGS          (DEVFS_FL_DEFAULT|DEVFS_FL_AUTO_DEVNUM)
> > 
> > 
> > The last one causes a compile error on i386 with CONFIG_DVB_DEVFS_ONLY 
> > enabled.
> 
> I thought I removed that config option, need to check whether that hunk
> got left.

Ok, here's the lost hunk:


--- 1.1/drivers/media/dvb/dvb-core/Kconfig	Wed Oct 30 02:16:55 2002
+++ edited/drivers/media/dvb/dvb-core/Kconfig	Tue Mar 18 16:56:51 2003
@@ -5,13 +5,3 @@
 	  DVB core utility functions for device handling, software fallbacks etc.
 
 	  Say Y when you have a DVB card and want to use it. If unsure say N.
-
-config DVB_DEVFS_ONLY
-	bool "devfs only"
-	depends on DVB_CORE=y && DEVFS_FS
-	help
-	  Drop support for old major/minor device scheme and support only devfs 
-	  systems. This saves some code.
-
-	  If unsure say N.
-
--- 1.3/drivers/media/dvb/dvb-core/dvbdev.c	Mon Nov 25 16:57:37 2002
+++ edited/drivers/media/dvb/dvb-core/dvbdev.c	Tue Mar 18 16:57:45 2003
@@ -21,8 +21,6 @@
  *
  */
 
-/*#define CONFIG_DVB_DEVFS_ONLY 1*/
-
 #include <linux/config.h>
 #include <linux/version.h>
 #include <linux/module.h>
@@ -56,17 +54,8 @@
 };
 
 
-#ifdef CONFIG_DVB_DEVFS_ONLY
-
-	#define DVB_MAX_IDS              ~0
-	#define nums2minor(num,type,id)  0
-	#define DVB_DEVFS_FLAGS          (DEVFS_FL_DEFAULT|DEVFS_FL_AUTO_DEVNUM)
-
-#else
-
-	#define DVB_MAX_IDS              4
-	#define nums2minor(num,type,id)  ((num << 6) | (id << 4) | type)
-	#define DVB_DEVFS_FLAGS          (DEVFS_FL_DEFAULT)
+#define DVB_MAX_IDS              4
+#define nums2minor(num,type,id)  ((num << 6) | (id << 4) | type)
 
 
 static
@@ -234,8 +223,7 @@
 
 	sprintf(name, "%s%d", dnames[type], id);
 	dvbdev->devfs_handle = devfs_register(adap->devfs_handle, name,
-					      DVB_DEVFS_FLAGS,
-					      DVB_MAJOR,
+					      0, DVB_MAJOR,
 					      nums2minor(adap->num, type, id),
 					      S_IFCHR | S_IRUSR | S_IWUSR,
 					      dvbdev->fops, dvbdev);

  reply	other threads:[~2003-03-18 15:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-17 22:31 Linux 2.5.65 Linus Torvalds
2003-03-18  0:53 ` John Cherry
2003-03-18  5:22 ` CaT
2003-03-18  8:15   ` Christoph Hellwig
2003-03-18  9:12     ` CaT
2003-03-18 10:08   ` Roman Zippel
2003-03-18 10:35     ` CaT
2003-03-18 10:43       ` Roman Zippel
2003-03-18 10:48       ` John Bradford
2003-03-18 15:16       ` Linus Torvalds
2003-03-18 15:33         ` CaT
2003-03-18 12:45 ` Remaining occurances of DEVFS_FL_AUTO_DEVNUM in 2.5.65 Adrian Bunk
2003-03-18 15:40   ` Christoph Hellwig
2003-03-18 16:04     ` Christoph Hellwig [this message]
2003-03-18 16:24 ` top Stack (l)users for 2.5.65 Jörn Engel

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=20030318170409.A7043@lst.de \
    --to=hch@lst.de \
    --cc=bunk@fs.tum.de \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox