From: Chris Wedgwood <cw@f00f.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>,
chris@freedom2surf.net, linux-kernel@vger.kernel.org
Subject: Re: Repeatable Oops in 2.4t13p4ac2
Date: Fri, 29 Dec 2000 14:56:36 +1300 [thread overview]
Message-ID: <20001229145636.C16930@metastasis.f00f.org> (raw)
In-Reply-To: <20001229144609.B16930@metastasis.f00f.org> <E14BoiI-0004ch-00@the-village.bc.nu>
In-Reply-To: <E14BoiI-0004ch-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Fri, Dec 29, 2000 at 01:52:07AM +0000
On Fri, Dec 29, 2000 at 01:52:07AM +0000, Alan Cox wrote:
The PCMCIA thing is unlikely to be related (there are no changes
on any PCMCIA that actually worked on 13pre4).
Oh, I'm sure it is unrelated -- it's just a good trigger for the
problem on my laptop.
Reiserfs might be the trigger because the quota code changed, but
if it did touch it I'd expect it to have failed to compile
No quotas, local version of reiserfs but probably not too divergent
from what else is out there.
I'm going to go and do a detailed audit of the mm bits I have
differing from Linus. For one I'd be much happier to differ in
drivers with Linus and avoid differing in mm/vm internals stuff.
I'll resync to t13p5 and any new reiserfs change that might be
relevant and see how that goes; if that works I'll start merging in
ac2 and see when it breaks.
--cw
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2000-12-29 2:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-28 13:20 chris
2000-12-28 11:56 ` Marcelo Tosatti
2000-12-28 15:48 ` Alan Cox
2000-12-28 14:36 ` Marcelo Tosatti
2000-12-28 16:45 ` Alan Cox
2000-12-28 15:06 ` Marcelo Tosatti
2000-12-28 17:18 ` Alan Cox
2000-12-28 18:08 ` chris
2000-12-28 16:31 ` Marcelo Tosatti
2000-12-29 1:46 ` Chris Wedgwood
2000-12-29 1:52 ` Alan Cox
2000-12-29 1:56 ` Chris Wedgwood [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=20001229145636.C16930@metastasis.f00f.org \
--to=cw@f00f.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=chris@freedom2surf.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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
all inboxes | Powered by JetHome®