From: "Ni@m" <niam.niam@gmail.com>
To: "Michal Piotrowski" <michal.k.k.piotrowski@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [1/2] 2.6.22-rc5: known regressions with patches v2
Date: Fri, 22 Jun 2007 14:39:50 +0300 [thread overview]
Message-ID: <a9e22dff0706220439m4bc70a30i8cc83fe92cff8bc9@mail.gmail.com> (raw)
In-Reply-To: <6bffcb0e0706220427p203de10epeaa6e97d3f63886d@mail.gmail.com>
> We have patches for "very high non-preempt latency in
> context_struct_compute_av()" and "list_add corruption. prev->next
> should be next (f7d28794), but was f0df8ed4 (prev=f0df8ed4) Kernel Bug
> at lib/list_debug.c:33", but both are too intrusive.
>
> Anyway, those bugs are not regressions.
>
Are you going to release 2.6.22 with this bugs?? But question wasn't
on this subject ...
The question was "why linux kernel release should have some bugs that
would be fixed fixed in future?"
Let's wait and publish kernel w/o known bugs. Let's wait for some
time, let's publish 2.6.22-rc_last, test it for some time(2 weeks for
example), fix bugs if any and after _test_period_of_whole_kernel_ but
not _separate_patches/parts_ of kernel release stable one!
next prev parent reply other threads:[~2007-06-22 11:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-21 16:35 Michal Piotrowski
2007-06-21 18:17 ` Linus Torvalds
2007-06-21 20:22 ` Michal Piotrowski
[not found] ` <a9e22dff0706220259y6b2cec29s8f5e059ba8c42b77@mail.gmail.com>
2007-06-22 10:21 ` Ni@m
[not found] ` <6bffcb0e0706220427p203de10epeaa6e97d3f63886d@mail.gmail.com>
2007-06-22 11:39 ` Ni@m [this message]
2007-06-22 11:54 ` Alan Cox
2007-06-22 12:03 ` Ni@m
2007-06-22 12:13 ` Michal Piotrowski
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=a9e22dff0706220439m4bc70a30i8cc83fe92cff8bc9@mail.gmail.com \
--to=niam.niam@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.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
Powered by JetHome