Linux bluetooth development
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Sid Boyce <g3vbv@blueyonder.co.uk>, Pavel Machek <pavel@ucw.cz>,
	Marcel Holtmann <marcel@holtmann.org>,
	linux-pm@lists.osdl.org, maxk@qualcomm.com,
	bluez-devel@lists.sourceforge.net, Mark Lord <lkml@rtr.ca>,
	Greg KH <greg@kroah.com>, Matt Mackall <mpm@selenic.com>,
	Johannes Berg <johannes@sipsolutions.net>,
	Albert Hopkins <kernel@marduk.letterboxes.org>,
	Ayaz Abdulla <aabdulla@nvidia.com>, Jeff Garzik <jeff@garzik.org>,
	netdev@vger.kernel.org
Subject: Re: [1/6] 2.6.21-rc2: known regressions
Date: Sun, 4 Mar 2007 18:26:19 -0800	[thread overview]
Message-ID: <20070304182619.6110bd74.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070305015031.GF3441@stusta.de>

On Mon, 5 Mar 2007 02:50:31 +0100 Adrian Bunk <bunk@stusta.de> wrote:

> This email lists some known regressions in 2.6.21-rc2 compared to 2.6.20
> that are not yet fixed in Linus' tree.


We seem to have broken an unusually large amount of stuff this time.

partial post-mortem:

- The ACPICA merge landed in -mm super-late: basically it was in mainline
  a week afterwards and saw only a single -mm release.

  Part of the reason for this short period in -mm was that ACPICA had its
  paws all over x86_64 code and conflicted badly with significant changes
  in the x86_64 tree.

  That happens sometimes.  But when it does, the mess lands in my lap
  rather than in the laps of the perpetrators.

  Lesson: keep the code well-factored so that different subsystems don't
  soil each others' kennels.

- The hrtimers/dynticks stuff is simply hard: timekeeping, low-level x86,
  even APICs.  These are areas in which things break a lot, so churning it
  was inevitably going to cause problems.

  Lesson: none, I think.  Low-level x86 support is just hard, and
  changing it breaks things.


So that accounts for _some_ of the damage, but I wonder if there's more to
it than that.

       reply	other threads:[~2007-03-05  2:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.64.0702272105220.12485@woody.linux-foundation.org>
     [not found] ` <20070305015031.GF3441@stusta.de>
2007-03-05  2:26   ` Andrew Morton [this message]
2007-03-05  3:35   ` [1/6] 2.6.21-rc2: known regressions Greg KH
2007-03-06  0:55     ` Johannes Berg
     [not found]   ` <45EB961D.6030808@rtr.ca>
2007-03-05  4:34     ` Greg KH
2007-03-05 12:42       ` Marcel Holtmann

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=20070304182619.6110bd74.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=aabdulla@nvidia.com \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=bunk@stusta.de \
    --cc=g3vbv@blueyonder.co.uk \
    --cc=greg@kroah.com \
    --cc=jeff@garzik.org \
    --cc=johannes@sipsolutions.net \
    --cc=kernel@marduk.letterboxes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.osdl.org \
    --cc=lkml@rtr.ca \
    --cc=marcel@holtmann.org \
    --cc=maxk@qualcomm.com \
    --cc=mpm@selenic.com \
    --cc=netdev@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --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