kernel-testers.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw-KKrjLPT3xs0@public.gmane.org>
To: Stephen Rothwell <sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>,
	kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Andrew Morton
	<akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
Subject: Re: linux-next: Tree for June 25
Date: Thu, 26 Jun 2008 02:28:38 +0200	[thread overview]
Message-ID: <200806260228.38674.rjw@sisk.pl> (raw)
In-Reply-To: <20080626003554.b2623aba.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>

On Wednesday, 25 of June 2008, Stephen Rothwell wrote:
> Hi all,

Hi,

> Changes since next-20080624:
> 
> The tip-core tree gained three conflicts against Linus' tree.
> 
> The sched tree gained a conflict against the cpus4096 tree.
> 
> The x86 tree gained a conflict against the ftrace tree.  It also required
> three patches that Ingo supplied.
> 
> The pci tree gained two conflicts against the x86 tree.
> 
> The v4l-dvb tree has had another commit reverted for a build problem,
> however that may have been due to a mismerge in yesterday's tree.
> 
> The acpi tree gained two conflicts against the x86 tree.
> 
> The tests tree gained a conflict against the sched tree.
> 
> The vfs tree gained a conflict against the sched tree.
> 
> The rr tree gained a conflict against each of the sched and powerpc
> trees.  It also required a patch and a commit reverted for build problems.
> 
> The pcmcia tree lost its conflict against Linus' tree.

This tree is completely broken on my test box (x86-64 HP nx6325) and I can't
even bisect it. :-(

It hits a NULL pointer dereference in find_symbol during boot, but when I tried
to bisect this issue, I hit another one that made the box hang solid during
boot (early, no messages available).

If things continue going this way, 2.6.27 will be a disaster ...

Thanks,
Rafael

       reply	other threads:[~2008-06-26  0:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080626003554.b2623aba.sfr@canb.auug.org.au>
     [not found] ` <20080626003554.b2623aba.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2008-06-26  0:28   ` Rafael J. Wysocki [this message]
2008-06-26  2:02     ` linux-next: Tree for June 25 Stephen Rothwell
     [not found]       ` <20080626120212.c8caa005.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2008-06-26  6:01         ` Rafael J. Wysocki
2008-06-26  6:59           ` Rafael J. Wysocki
2008-06-26 10:03             ` Jiri Kosina
2008-06-26 10:49               ` Rafael J. Wysocki
     [not found]                 ` <200806261249.24340.rjw-KKrjLPT3xs0@public.gmane.org>
2008-06-26 14:21                   ` Stephen Rothwell
2008-06-26 18:23                     ` Rafael J. Wysocki
     [not found]               ` <alpine.LRH.1.10.0806261201420.10290-1ReQVI26iDCaZKY3DrU6dA@public.gmane.org>
2008-06-27  3:01                 ` Rusty Russell

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=200806260228.38674.rjw@sisk.pl \
    --to=rjw-kkrjlpt3xs0@public.gmane.org \
    --cc=akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
    --cc=kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).