public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nigel Kukard <nkukard@lbsd.net>
To: Chris Wright <chrisw@osdl.org>
Cc: "Kevin P. Fleming" <kpfleming@backtobasicsmgmt.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [2.6.3] Sysfs breakage - tun.ko
Date: Thu, 4 Mar 2004 07:25:26 +0200	[thread overview]
Message-ID: <20040304052526.GT21950@lbsd.net> (raw)
In-Reply-To: <20040302182834.R22989@build.pdx.osdl.net>

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

Thanks bud!

Hopefully it'll get included in 2.6.4  ;)

On Tue, Mar 02, 2004 at 06:28:34PM -0800, Chris Wright wrote:
> * Nigel Kukard (nkukard@lbsd.net) wrote:
> > 
> > Nothing said solves the problem, the problem has got nothing to do with
> > devfs (only for compat reasons), the problem is that "net/tun" breaks
> > sysfs.
> 
> Yes, why does this not work?  Keeps devfs legacy name, works fine with
> udev, and makes proper dir in sysfs.
> 
> thanks,
> -chris
> 
> ===== drivers/net/tun.c 1.29 vs edited =====
> --- 1.29/drivers/net/tun.c	Sat Jan 10 16:09:09 2004
> +++ edited/drivers/net/tun.c	Tue Mar  2 12:05:30 2004
> @@ -602,7 +602,8 @@
>  
>  static struct miscdevice tun_miscdev = {
>  	.minor = TUN_MINOR,
> -	.name = "net/tun",
> +	.name = "tun",
> +	.devfs_name = "net/tun",
>  	.fops = &tun_fops
>  };
>  

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2004-03-04  5:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-01 19:48 [2.6.3] Sysfs breakage - tun.ko Nigel Kukard
2004-03-01 20:20 ` Kevin P. Fleming
2004-03-01 20:24   ` Nigel Kukard
2004-03-01 20:47   ` Chris Wright
2004-03-01 21:08     ` Kevin P. Fleming
2004-03-02  0:32   ` H. Peter Anvin
2004-03-02  6:02   ` Nigel Kukard
2004-03-03  2:28     ` Chris Wright
2004-03-04  5:25       ` Nigel Kukard [this message]

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=20040304052526.GT21950@lbsd.net \
    --to=nkukard@lbsd.net \
    --cc=chrisw@osdl.org \
    --cc=kpfleming@backtobasicsmgmt.com \
    --cc=linux-kernel@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