From: "Michal Piotrowski" <michal.k.k.piotrowski@gmail.com>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: "Ni@m" <niam.niam@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:13:59 +0200 [thread overview]
Message-ID: <6bffcb0e0706220513n50740fedrce56467f72718dcd@mail.gmail.com> (raw)
In-Reply-To: <20070622125428.28934ee0@the-village.bc.nu>
On 22/06/07, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> On Fri, 22 Jun 2007 14:39:50 +0300
> "Ni@m" <niam.niam@gmail.com> wrote:
>
> > > 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.
> > The question was "why linux kernel release should have some bugs that
> > would be fixed fixed in future?"
>
> Because those bug fixes are intrusive so will potentially cause more
> other bugs that will need fixing - so make the kernel a worse not a
> better one in the short term.
>
> > Let's wait and publish kernel w/o known bugs.
>
> That would be a bit like waiting for a Debian release and never happen.
I'm trying to imagine this - Linux 2.6 "Debian style" roadmap:
15-VII-2007 - release of Linux 2.6.22
1-VIII-2007 - freeze
15-II-2009 - release of Linux 2.6.23
1-III-2009 - freeze
1-IX-2010 - release of Linux 2.6.24
:)
>
> Alan
>
Regards,
Michal
--
LOG
http://www.stardust.webpages.pl/log/
prev parent reply other threads:[~2007-06-22 12:14 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
2007-06-22 11:54 ` Alan Cox
2007-06-22 12:03 ` Ni@m
2007-06-22 12:13 ` Michal Piotrowski [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=6bffcb0e0706220513n50740fedrce56467f72718dcd@mail.gmail.com \
--to=michal.k.k.piotrowski@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=niam.niam@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
all inboxes | Powered by JetHome®