From: Ralf Baechle <ralf@linux-mips.org>
To: Giuseppe Sacco <giuseppe@eppesuigoccas.homedns.org>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
linux-mips@linux-mips.org
Subject: Re: Compiler error? [was: Re: new kernel oops in recent kernels]
Date: Mon, 17 Mar 2008 14:18:28 +0000 [thread overview]
Message-ID: <20080317141828.GA25798@linux-mips.org> (raw)
In-Reply-To: <1205741142.3515.2.camel@localhost>
On Mon, Mar 17, 2008 at 09:05:42AM +0100, Giuseppe Sacco wrote:
> The patch you proposed, that use a larger buffer, does not seems to
> trigger the bug.
It may help but doesn't have a chance to be accepted upstream. So
this is no more than an useful litmus test.
Ralf
next prev parent reply other threads:[~2008-03-17 14:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-16 10:49 new kernel oops in recent kernels Giuseppe Sacco
2008-03-16 20:27 ` Compiler error? [was: Re: new kernel oops in recent kernels] Giuseppe Sacco
2008-03-16 23:36 ` Thomas Bogendoerfer
2008-03-17 8:05 ` Giuseppe Sacco
2008-03-17 14:18 ` Ralf Baechle [this message]
2008-03-17 14:32 ` Thomas Bogendoerfer
2008-03-21 23:00 ` Thomas Bogendoerfer
2008-03-22 23:39 ` Giuseppe Sacco
2008-03-23 11:16 ` Thomas Bogendoerfer
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=20080317141828.GA25798@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=giuseppe@eppesuigoccas.homedns.org \
--cc=linux-mips@linux-mips.org \
--cc=tsbogend@alpha.franken.de \
/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