public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Steven J. Hill" <sjhill@cotw.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: mtd@infradead.org
Subject: Re: MTD CVS update: 'mtd/kernel mtdblock.c'
Date: Tue, 24 Oct 2000 06:46:02 -0500	[thread overview]
Message-ID: <39F5767A.48E1A44C@cotw.com> (raw)
In-Reply-To: 18079.972375290@redhat.com

David Woodhouse wrote:
> 
> *(int *)0=0; doesn't cause an oops on all platforms. That was why BUG() was
> introduced. Probably better just to omit my paranoia checks altogether,
> once we're happy that mtdblock actually works. For now, surround them in
> #ifdef PARANOIA. I thought I'd done that already.
> 
Alright, will do.

> DECLARE_MUTEX_LOCKED wants adding to compatmac.h if it's not already there.
> 
Will do.

> What was the reasoning for removing the 'static' from the declaration of
> thr_wq?
> 
Uhhh...that would be my stupidity. I forgot to put 'static' back on
the declaration.

-Steve

-- 
 Steven J. Hill - Embedded SW Engineer
 Public Key: 'finger sjhill@mail.cotw.com'
 FPR1: E124 6E1C AF8E 7802 A815
 FPR2: 7D72 829C 3386 4C4A E17D


To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

  reply	other threads:[~2000-10-24 11:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E13nksk-0002RR-00@infradead.org>
2000-10-24  8:14 ` MTD CVS update: 'mtd/kernel mtdblock.c' David Woodhouse
2000-10-24 11:46   ` Steven J. Hill [this message]
2000-10-24 16:25     ` Proper way of setting MTD_DEBUG Bradley D. LaRonde
2000-10-24 18:59       ` Steven J. Hill
2000-10-24 18:57         ` Bradley D. LaRonde
2000-06-23  9:34 MTD CVS update: 'mtd/kernel mtdblock.c' David Woodhouse
  -- strict thread matches above, loose matches on Subject: below --
2000-05-03 14:57 David Woodhouse

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=39F5767A.48E1A44C@cotw.com \
    --to=sjhill@cotw.com \
    --cc=dwmw2@infradead.org \
    --cc=mtd@infradead.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