From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
kernel-testers@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Jaswinder Singh <jaswinder@infradead.org>,
David Woodhouse <David.Woodhouse@intel.com>,
"Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: linux-next: Tree for June 26
Date: Fri, 27 Jun 2008 01:38:52 +0200 [thread overview]
Message-ID: <200806270138.53895.rjw@sisk.pl> (raw)
In-Reply-To: <20080627010842.e1a0c4b5.sfr@canb.auug.org.au>
On Thursday, 26 of June 2008, Stephen Rothwell wrote:
> Hi all,
>
> Changes since next-20080625:
>
> The tip-core tree lost its three conflicts against Linus' tree.
>
> The pci tree gained two conflicts against the x86 tree.
>
> The v4l-dvb tree had the second revert undone. We will see if this is
> right.
>
> The net tree gained a conflict against the wireless-current tree.
>
> The vfs tree lost its conflict against the sched tree.
>
> The arm tree lost its conflict against Linus' tree.
>
> The rr tree gained a patch for a build problem instead the revert.
>
> The firmware tree lost a conflict against the usb tree.
commit 423c982fffb1cd95c8cdd654ce5ab59351ba41f5
Author: Jaswinder Singh <jaswinder@infradead.org>
Date: Wed Jun 18 19:58:33 2008 +0530
firmware: convert tg3 driver to request_firmware()
breaks my nx6325.
Apparently, with this patch applied the tg3 has a NULL pointer dereference
somewhere, but I can only see the first line of the oops, afterwards the box
hangs solid.
Please drop it if possible.
Also, arch/x86/kernel/io_apic_64.c seems wrong at the moment, as it checks
for conditions that are never satisfied etc.
Thanks,
Rafael
next prev parent reply other threads:[~2008-06-26 23:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-26 15:08 Stephen Rothwell
2008-06-26 23:38 ` Rafael J. Wysocki [this message]
2008-06-27 9:28 ` David Woodhouse
2008-06-27 10:51 ` David Woodhouse
2008-06-27 12:42 ` Kamalesh Babulal
2008-06-27 12:48 ` David Woodhouse
2008-06-27 23:04 ` Rafael J. Wysocki
2008-06-28 9:54 ` Jaswinder Singh
2008-06-28 10:32 ` David Woodhouse
2008-06-29 0:15 ` Rafael J. Wysocki
2008-06-29 8:01 ` David Woodhouse
2008-06-29 11:36 ` Rafael J. Wysocki
2008-06-29 20:49 ` David Woodhouse
2008-06-28 14:51 ` Ingo Molnar
2008-06-28 10:09 ` David Woodhouse
2009-06-26 5:46 Stephen Rothwell
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=200806270138.53895.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=David.Woodhouse@intel.com \
--cc=akpm@linux-foundation.org \
--cc=jaswinder@infradead.org \
--cc=kernel-testers@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=mingo@elte.hu \
--cc=sfr@canb.auug.org.au \
/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®