From: Christoph Hellwig <hch@infradead.org>
To: Bernd Schubert <bernd-schubert@web.de>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: 2.6.7 oops, sk98lin related?
Date: Thu, 22 Jul 2004 16:03:14 +0100 [thread overview]
Message-ID: <20040722150314.GB13195@infradead.org> (raw)
In-Reply-To: <200407221101.16388.bernd-schubert@web.de>
On Thu, Jul 22, 2004 at 11:01:14AM +0200, Bernd Schubert wrote:
> Hello Christoph and all others,
>
> is this an sk98lin oops, maybe related to your patches or is it a completely
> different problem?
I don't think there's skge patches from me in 2.6.7 yet, but certainly not
in that area ;-)
This is just a big memory allocation failing, not an oops anyway.
next prev parent reply other threads:[~2004-07-22 15:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-22 9:01 2.6.7 oops, sk98lin related? Bernd Schubert
2004-07-22 15:03 ` Christoph Hellwig [this message]
2004-07-22 17:08 ` Bernd Schubert
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=20040722150314.GB13195@infradead.org \
--to=hch@infradead.org \
--cc=bernd-schubert@web.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).