From: "Rafael J. Wysocki" <firstname.lastname@example.org>
To: Stephen Rothwell <email@example.com>
Cc: firstname.lastname@example.org, LKML <email@example.com>,
Bartlomiej Zolnierkiewicz <firstname.lastname@example.org>,
Jens Axboe <email@example.com>,
Borislav Petkov <firstname.lastname@example.org>,
FUJITA Tomonori <email@example.com>,
Andrew Morton <firstname.lastname@example.org>
Subject: Re: linux-next: Tree for May 22
Date: Fri, 23 May 2008 03:27:49 +0200 [thread overview]
Message-ID: <email@example.com> (raw)
On Thursday, 22 of May 2008, Stephen Rothwell wrote:
> Hi all,
> Changes since next-20080522:
> The three patches reverted from the driver-core tree yesterday have been
> removed from there.
> The net tree (actually the wireless tree) had a trivial conflict with the
> wireless-current tree.
> One of the sound tree build patches has been merged.
> The semaphore-removal tree still needed three patches reverted because similar
> patches were merged into upstream and the scsi-rc-fixes trees.
> The bkl-removal tree had a conflict with the arm tree because the arm
> tree removed a file that was changed.
> I have applied the following temporary patch for known build problems:
> "Fix various 8390 builds" - the net tree broke builds on various
> architectures - hopefully this patch will go into the net tree shortly.
> "build failure with netfilter on __nf_ct_helper_find()" - breakage
> due to the moving of stuff from list.h to rculist.h
This one and the previous linux-next can't resume from suspend to RAM on my
HP nx6325. The problem is reliably reproducible 100% of the time.
The patch that causes it to happen, as identified by bisection, is:
Author: Bartlomiej Zolnierkiewicz <firstname.lastname@example.org>
Date: Thu May 22 10:40:19 2008 +1000
ide: use __generic_unplug_device() in ide_do_drive_cmd()
Cc: FUJITA Tomonori <email@example.com>
Cc: Borislav Petkov <firstname.lastname@example.org>
Cc: Jens Axboe <email@example.com>
Signed-off-by: Bartlomiej Zolnierkiewicz <firstname.lastname@example.org>
Reverting it along with the next IDE patches (up to and including
"ide: remove action argument in ide_do_drive_cmd") makes the problem go away.
next prev parent reply other threads:[~2008-05-23 1:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-22 6:52 linux-next: Tree for May 22 Stephen Rothwell
2008-05-23 1:27 ` Rafael J. Wysocki [this message]
2008-05-25 21:55 ` Bartlomiej Zolnierkiewicz
2008-05-25 8:03 ` Borislav Petkov
2008-05-25 12:23 ` Rafael J. Wysocki
2009-05-22 8:51 Stephen Rothwell
2010-05-22 7:04 Stephen Rothwell
2013-05-22 6:01 Stephen Rothwell
2013-05-22 7:19 ` Xiong Zhou
2014-05-22 10:46 Stephen Rothwell
2015-05-22 8:09 Stephen Rothwell
2017-05-22 6:04 Stephen Rothwell
2019-05-22 3:40 Stephen Rothwell
2020-05-22 12:52 Stephen Rothwell
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).