From: Adrian Bunk <bunk@kernel.org>
To: Mark Lord <lkml@rtr.ca>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Natalie Protasevich <protasnb@gmail.com>
Subject: Re: 2.6.25-rc7-git5: Reported regressions from 2.6.24
Date: Mon, 31 Mar 2008 22:35:16 +0300 [thread overview]
Message-ID: <20080331193516.GC23259@cs181133002.pp.htv.fi> (raw)
In-Reply-To: <47F13A5A.7040305@rtr.ca>
On Mon, Mar 31, 2008 at 03:24:10PM -0400, Mark Lord wrote:
> Adrian Bunk wrote:
>> On Mon, Mar 31, 2008 at 01:48:15PM -0400, Mark Lord wrote:
>>> Rafael,
>>>
>>> Add this one to the list?
>>
>>
>> That's not a regression from 2.6.24
> ..
>
> 2.6.24 does not flood my syslog with those messages.
> 2.6.25-rc* does. Looks like a regression.
>
> The original bug was a hidden regression in 2.6.23,
> which nobody bothered to identify until now.
Let's try to get this patch into Linus' tree without arguing
whether it might be called a post 2.6.24 regression or not. ;)
> Just because some code "gets away with" a regression
> for a kernel or two, doesn't mean that regression shouldn't be fixed.
No disagreement on this one.
We already have over 200 known (and many more once reported) regressions
in the kernel, and all of them should be fixed...
> Cheers
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2008-03-31 19:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-31 0:28 Rafael J. Wysocki
2008-03-31 17:48 ` Mark Lord
2008-03-31 19:17 ` Adrian Bunk
2008-03-31 19:24 ` Mark Lord
2008-03-31 19:35 ` Adrian Bunk [this message]
2008-03-31 20:31 ` Rafael J. Wysocki
2008-04-02 21:00 ` Bongani Hlope
2008-04-02 21:57 ` Rafael J. Wysocki
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=20080331193516.GC23259@cs181133002.pp.htv.fi \
--to=bunk@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
--cc=protasnb@gmail.com \
--cc=rjw@sisk.pl \
--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®