linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: Bryan Wu <cooloney.lkml@gmail.com>
Cc: Robin Getz <rgetz@blackfin.uclinux.org>,
	Bryan Wu <bryan.wu@analog.com>,
	linux-kernel@vger.kernel.org,
	Mike Frysinger <michael.frysinger@analog.com>
Subject: Re: [PATCH 1/1] [Blackfin] char driver for Blackfin on-chip OTP memory
Date: Wed, 30 Jan 2008 14:43:57 +0100	[thread overview]
Message-ID: <47A07F1D.9000208@gmail.com> (raw)
In-Reply-To: <386072610801300515j56d10f2ej55859500c91befbb@mail.gmail.com>

On 01/30/2008 02:15 PM, Bryan Wu wrote:
> And one question for Jiri, what is the difference between misc char
> driver with other char drivers.

No difference in behaviour. Open function in misc replaces fops by your 
specified one (like a v4l or tty layer, or chrdev_open aswell, which will be 
called on each character device open).

> Because we got some other char drivers locally, maybe some day send them out.

Misc has one predefined major and is used for such uses, in which you need only 
one minor number. The point is not to block resting 254 minors of one major just 
for only one minor used.

  reply	other threads:[~2008-01-30 13:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-30 10:36 [PATCH 1/1] [Blackfin] char driver for Blackfin on-chip OTP memory Bryan Wu
2008-01-30 11:00 ` Jiri Slaby
2008-01-30 12:39   ` Robin Getz
2008-01-30 13:08     ` Jiri Slaby
2008-01-30 13:15     ` Bryan Wu
2008-01-30 13:43       ` Jiri Slaby [this message]
2008-01-30 13:53         ` Jiri Slaby
2008-01-30 13:19   ` Mike Frysinger
2008-01-30 13:38     ` Jiri Slaby
2008-01-30 13:41       ` Mike Frysinger
2008-02-05 18:59   ` Mike Frysinger

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=47A07F1D.9000208@gmail.com \
    --to=jirislaby@gmail.com \
    --cc=bryan.wu@analog.com \
    --cc=cooloney.lkml@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael.frysinger@analog.com \
    --cc=rgetz@blackfin.uclinux.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;
as well as URLs for NNTP newsgroup(s).