From: Jeff Garzik <jgarzik@pobox.com>
To: Andrew Morton <akpm@osdl.org>
Cc: torvalds@osdl.org, linux-ide@vger.kernel.org,
linux-kernel@vger.kernel.org,
Reuben Farrelly <reuben-lkml@reub.net>
Subject: Re: [git patches] 2.6.x libata updates
Date: Wed, 18 Jan 2006 00:18:57 -0500 [thread overview]
Message-ID: <43CDCFC1.2000008@pobox.com> (raw)
In-Reply-To: <20060117183318.1031c0d2.akpm@osdl.org>
Andrew Morton wrote:
> Jeff Garzik <jgarzik@pobox.com> wrote:
>
>> Please pull from 'upstream-linus' branch of
>> master.kernel.org:/pub/scm/linux/kernel/git/jgarzik/libata-dev.git
>
>
> I worry that whatever it is which has busted Reuben's machine will leak
> into mainline. This patch probably isn't it.
Nothing at all in this push is remotely controversial...
> I guess if we can feed libata and acpi into mainline in little bits and
> pieces like this, that'll help us work out the cause.
>
> Reuben has spent ages bisecting lots of patches, but the bug is quite
> intermittent, which makes the process quite maddeningly error-prone and
> slow.
>
> Then again, perhaps merging it up is the best way of fixing it: someone out
> there will hit the thing more repeatably and will have a better shot at
> finding the cause.
Well, I haven't even looked at ACPI yet, and the Jens/Tejun stuff didn't
get much testing at all. There's a lot of unfamiliar stuff in the mix.
Jeff
next prev parent reply other threads:[~2006-01-18 5:19 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-18 2:15 [git patches] 2.6.x libata updates Jeff Garzik
2006-01-18 2:33 ` Andrew Morton
2006-01-18 5:18 ` Jeff Garzik [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-03 16:43 Jeff Garzik
2006-01-03 16:51 ` Bartlomiej Zolnierkiewicz
2006-01-03 16:56 ` Jeff Garzik
2006-01-03 17:32 ` Alan Cox
2006-01-03 17:43 ` Jeff Garzik
2006-01-03 18:35 ` Bartlomiej Zolnierkiewicz
2006-01-03 18:50 ` Alan Cox
2006-01-04 14:02 ` Alan Cox
2006-01-04 20:35 ` Matt Darcy
2006-01-04 22:25 ` Matt Darcy
2006-01-05 18:44 ` Terrence Martin
2006-01-05 20:29 ` Roman Gischig
2005-11-11 16:23 Jeff Garzik
2005-11-09 6:54 Jeff Garzik
2005-10-29 18:22 Jeff Garzik
2005-10-29 19:14 ` Andrew Morton
2005-10-29 19:20 ` Jeff Garzik
2005-10-29 19:37 ` Linus Torvalds
2005-10-29 20:09 ` Al Viro
2005-10-29 20:16 ` Jeff Garzik
2005-10-29 22:21 ` Andrew Morton
2005-10-29 22:30 ` Linus Torvalds
2005-10-30 0:55 ` Tony Luck
2005-10-30 2:28 ` Horst von Brand
2005-10-30 12:44 ` Rob Landley
2005-10-30 22:36 ` Linus Torvalds
2005-10-30 23:31 ` Rob Landley
2005-10-31 0:58 ` Linus Torvalds
2005-10-31 2:35 ` Rob Landley
2005-11-10 0:36 ` Matthias Urlichs
2005-10-30 23:59 ` Rob Landley
2005-10-31 0:16 ` Randy.Dunlap
2005-10-30 13:11 ` Pavel Machek
2005-10-31 3:55 ` David Lang
2005-10-28 0:49 Jeff Garzik
2005-10-28 16:08 ` Linus Torvalds
2005-08-29 0:25 Jeff Garzik
2005-06-28 16:59 Jeff Garzik
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=43CDCFC1.2000008@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@osdl.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=reuben-lkml@reub.net \
--cc=torvalds@osdl.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).