public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-kernel@vger.kernel.org, fuse-devel@lists.sourceforge.net,
	akpm@linux-foundation.org, greg@kroah.com
Subject: Re: [PATCH 5/5] CUSE: implement CUSE - Character device in Userspace
Date: Sat, 22 Nov 2008 14:05:40 +0900	[thread overview]
Message-ID: <49279324.7010605@kernel.org> (raw)
In-Reply-To: <E1L3bA9-0000Dx-Vb@pomaz-ex.szeredi.hu>

Miklos Szeredi wrote:
> On Thu, 20 Nov 2008, Tejun Heo wrote:
>> diff --git a/include/linux/miscdevice.h b/include/linux/miscdevice.h
>> index 0be9245..d4dcca8 100644
>> --- a/include/linux/miscdevice.h
>> +++ b/include/linux/miscdevice.h
>> @@ -28,6 +28,7 @@
>>  #define MPT_MINOR		220
>>  #define	HPET_MINOR		228
>>  #define FUSE_MINOR		229
>> +#define CUSE_MINOR		230
> 
> This doesn't work: device numbers have to be allocated by LANANA.

My last attempt at LANANA for extended devt didn't get me anywhere and
I'm not sure LANANA is handling miscdevice minors at all.  If you go
through the tree, there are quite a few duplicate allocations including
FUSE_MINOR.  At any rate, we can definitely try LANANA.

> But maybe we can get away with a dynamic number, now that everyone
> uses udev?

It would still be nice to have static /dev/cuse and trying to open it
can trigger "modprobe cuse".  It's not like we're short of device number
space anyway.

Thanks.

-- 
tejun

  reply	other threads:[~2008-11-22  5:05 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-20 14:22 [PATCHSET] CUSE: implement CUSE, take #2 Tejun Heo
2008-11-20 14:22 ` [PATCH 1/5] FUSE: add fuse_ prefix to several functions Tejun Heo
2008-11-20 14:23 ` [PATCH 2/5] FUSE: export symbols to be used by CUSE Tejun Heo
2008-11-22  8:05   ` [PATCH 2/5 UPDATED] " Tejun Heo
2008-11-20 14:23 ` [PATCH 3/5] FUSE: separate out fuse_conn_init() from new_conn() Tejun Heo
2008-11-20 14:23 ` [PATCH 4/5] FUSE: add fuse_conn->release() Tejun Heo
2008-11-20 14:23 ` [PATCH 5/5] CUSE: implement CUSE - Character device in Userspace Tejun Heo
2008-11-21 18:55   ` Miklos Szeredi
2008-11-22  5:05     ` Tejun Heo [this message]
2008-11-22  5:17       ` Andrew Morton
2008-11-22  7:29         ` Tejun Heo
2008-11-22  8:40       ` Miklos Szeredi
2008-11-22  8:48         ` Tejun Heo
2008-11-22  5:16   ` Andrew Morton
2008-11-22  8:02     ` Tejun Heo
2008-11-22  8:07       ` [PATCH 5/5 UPDATED] " Tejun Heo
2008-11-26 10:02         ` Miklos Szeredi
2008-11-26 10:17           ` Tejun Heo
2008-11-26 11:34             ` Miklos Szeredi
  -- strict thread matches above, loose matches on Subject: below --
2008-08-28 18:18 [PATCHSET] CUSE: implement CUSE Tejun Heo
2008-08-28 18:19 ` [PATCH 5/5] CUSE: implement CUSE - Character device in Userspace Tejun Heo
2008-08-28 20:07   ` Andrew Morton
2008-08-28 22:15     ` Greg KH
2008-08-28 22:32       ` Andrew Morton
2008-08-29  2:09     ` Tejun Heo
2008-08-29  2:20       ` Andrew Morton
2008-08-29 15:27       ` Nick Bowler

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=49279324.7010605@kernel.org \
    --to=tj@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=fuse-devel@lists.sourceforge.net \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    /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