From: Dave Chinner <david@fromorbit.com>
To: Donald Douwsma <donaldd@sgi.com>
Cc: Eric Sandeen <sandeen@sandeen.net>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH] re-remove xfs custom bitops
Date: Thu, 10 Jul 2008 16:05:06 +1000 [thread overview]
Message-ID: <20080710060506.GW11558@disturbed> (raw)
In-Reply-To: <48759813.2080601@sgi.com>
On Thu, Jul 10, 2008 at 03:03:15PM +1000, Donald Douwsma wrote:
> Donald Douwsma wrote:
>> Eric Sandeen wrote:
>>> Donald Douwsma wrote:
>>>
>>>> First time round I hit an Oops on xfstests/177 while running the
>>>> auto group
>>>> on ppc32. I dont seem to hit it running the single test, its
>>>> intermittent.
>>>
>>> Funky. Do you ever hit it w/ the patch reverted?
>>
>> That's the question. So far no, the QA guys said they hit it a while
>> ago, but the time frame still matches last time. I dont think this
>> is related but I need to get some more ppc32 runs without.
>>
>> I'm probably being over cautious but I'd like to avoid the
>> inagain/outagain/inagain/outagain approach we keep using with
>> some of these cleanups.
>>
>> Don
>>
>
> Ok I hit the Oops again last weekend without the patch.
> Which means I have a patch to checkin and another bug to fix Yea!
>
> Dave, Eric said this should still be considered signed-off-by you,
> You ok with that?
Yeah, no problems there.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2008-07-10 6:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-23 3:57 [PATCH] re-remove xfs custom bitops Eric Sandeen
2008-05-13 16:35 ` Eric Sandeen
2008-05-15 8:45 ` Donald Douwsma
2008-06-28 20:08 ` Eric Sandeen
2008-06-30 9:02 ` Donald Douwsma
2008-07-03 1:58 ` Eric Sandeen
2008-07-03 6:46 ` Donald Douwsma
2008-07-03 15:02 ` Eric Sandeen
2008-07-10 5:03 ` Donald Douwsma
2008-07-10 5:10 ` Eric Sandeen
2008-07-10 6:05 ` Dave Chinner [this message]
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=20080710060506.GW11558@disturbed \
--to=david@fromorbit.com \
--cc=donaldd@sgi.com \
--cc=sandeen@sandeen.net \
--cc=xfs@oss.sgi.com \
/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