public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: Russell King <rmk+lkml@arm.linux.org.uk>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: MMC block major dev
Date: Wed, 01 Sep 2004 13:18:19 +0100	[thread overview]
Message-ID: <1094041098.2476.58.camel@localhost.localdomain> (raw)
In-Reply-To: <4134CDF0.7070600@drzeus.cx>

On Maw, 2004-08-31 at 20:13, Pierre Ossman wrote:
> Some debug statements revealed that the driver ended up on major number 
> 254. I'm not familiar with how kernel memory is initialized but using an 
> uninitialized variable should result in random numbers. It seems to get 
> 254 each time though. Can I count on this? (i.e. can I safely create 
> device node files with this major).

No.


      parent reply	other threads:[~2004-09-01 13:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-31 19:13 MMC block major dev Pierre Ossman
2004-08-31 19:15 ` Russell King
2004-08-31 19:47   ` Pierre Ossman
2004-09-01 12:16     ` Alan Cox
2004-09-01 21:55       ` Russell King
2004-09-01 21:28         ` Alan Cox
2004-09-01 12:18 ` Alan Cox [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=1094041098.2476.58.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=drzeus-list@drzeus.cx \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk+lkml@arm.linux.org.uk \
    /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