From: James Bottomley <James.Bottomley@SteelEye.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: "Michal Piotrowski" <michal.k.k.piotrowski@gmail.com>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
"Toralf Förster" <toralf.foerster@gmx.de>
Subject: Re: [1/3] 2.6.22-rc3: known regressions v2
Date: Tue, 05 Jun 2007 10:16:45 -0500 [thread overview]
Message-ID: <1181056605.3668.29.camel@mulgrave.il.steeleye.com> (raw)
In-Reply-To: <20070602161337.46f267da.randy.dunlap@oracle.com>
On Sat, 2007-06-02 at 16:13 -0700, Randy Dunlap wrote:
> On Fri, 01 Jun 2007 14:20:44 +0200 Michal Piotrowski wrote:
>
> > Hi all,
> >
> > Here is a list of some known regressions in 2.6.22-rc3.
> >
> > Feel free to add new regressions/remove fixed etc.
> > http://kernelnewbies.org/known_regressions
> >
> >
> > Unclassified
> >
> > Subject : build failed in function `vic_sys_interrupt'
> > References : http://lkml.org/lkml/2007/5/31/227
> > Submitter : Toralf Förster <toralf.foerster@gmx.de>
> > Status : Unknown
>
> I probably wouldn't call a randconfig build problem a regression.
>
> James, does Voyager support SMP=n now?
No, this is a longstanding bug that I keep meaning to find time to fix.
James
prev parent reply other threads:[~2007-06-05 15:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-01 12:20 Michal Piotrowski
2007-06-01 13:00 ` Miklos Szeredi
2007-06-01 13:03 ` Ingo Molnar
2007-06-01 21:23 ` Miklos Szeredi
[not found] ` <b6a2187b0706010628m3d9ffad5y9a76e22719f439b7@mail.gmail.com>
[not found] ` <6bffcb0e0706010923y5a2bc729x7388b60cc73d94f7@mail.gmail.com>
2007-06-01 16:43 ` Jeff Chua
2007-06-01 17:10 ` Sam Ravnborg
2007-06-01 21:03 ` Jeff Chua
2007-06-01 20:48 ` Michael Buesch
2007-06-02 23:13 ` Randy Dunlap
2007-06-05 15:16 ` James Bottomley [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=1181056605.3668.29.camel@mulgrave.il.steeleye.com \
--to=james.bottomley@steeleye.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=randy.dunlap@oracle.com \
--cc=toralf.foerster@gmx.de \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®