public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: sjhill@cotw.com
Cc: mtd@infradead.org
Subject: Re: MTD CVS update: 'mtd/kernel mtdblock.c'
Date: Tue, 24 Oct 2000 09:14:50 +0100	[thread overview]
Message-ID: <18079.972375290@redhat.com> (raw)
In-Reply-To: <E13nksk-0002RR-00@infradead.org>


sjhill@cotw.com said:
>  Made changes so that 'mtdblock' would build with 2.2.x kernels again
> and not only on ARM platforms. People PLEASE remember that this code
> is used in two different kernel trees AND on different CPU
> architectures. 

*(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.

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

What was the reasoning for removing the 'static' from the declaration of 
thr_wq?

Anyway, it didn't build _only_ on ARM - it built on SH too :)

--
dwmw2




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

       reply	other threads:[~2000-10-24  8:15 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 ` David Woodhouse [this message]
2000-10-24 11:46   ` MTD CVS update: 'mtd/kernel mtdblock.c' Steven J. Hill
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=18079.972375290@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=mtd@infradead.org \
    --cc=sjhill@cotw.com \
    /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