From: Chris Mason <chris.mason@oracle.com>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: Eric Sandeen <sandeen@sandeen.net>, wk <handygewinnspiel@gmx.de>,
Matthew Wilcox <matthew@wil.cx>,
Andrew Morton <akpm@linux-foundation.org>,
rjw@sisk.pl, HWerner4@gmx.de, viro@zeniv.linux.org.uk,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
mchehab@infradead.org
Subject: Re: [linux-dvb] compiling on 2.6.28 broken?
Date: Wed, 14 Jan 2009 20:54:38 -0500 [thread overview]
Message-ID: <1231984478.8269.57.camel@think.oraclecorp.com> (raw)
In-Reply-To: <ac3eb2510901141500w5950c61dyba8af2e1d515ee08@mail.gmail.com>
On Thu, 2009-01-15 at 00:00 +0100, Kay Sievers wrote:
> On Wed, Jan 14, 2009 at 22:40, Chris Mason <chris.mason@oracle.com> wrote:
> > On Wed, 2009-01-14 at 15:35 -0600, Eric Sandeen wrote:
> >
> >> >> Attached the log from stracing the command which was ivoked by the
> >> >> Makefile from v4l-dvb.
> >> >> I guess this is all i could contribute to that problem. Thats stuff for
> >> >> xfs filesystem experts now..
> >> >
> >> > Seems suspect indeed. Could you please attach the strace for the run
> >> > that works on the older kernel?
> >>
> >> Chris got my attention on this one; you probably want this fix from hch:
> >>
> >> http://oss.sgi.com/archives/xfs/2009-01/msg00158.html
> >
> > Seems like this one should get queued for -stable as well if it isn't
> > already.
>
> Chris, is this similar to the thing we've seen with btrfs? Is this fixed?
Similar yes, although I can't blame my bug on David Woodhouse. Not
fixed yet, but I'll jump on it this week.
-chris
next prev parent reply other threads:[~2009-01-15 1:55 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090112190420.51f75853@pedra.chehab.org>
[not found] ` <20090112132130.6c932b85.akpm@linux-foundation.org>
[not found] ` <20090112220624.4fbfee34@pedra.chehab.org>
[not found] ` <20090112162337.318dd61d.akpm@linux-foundation.org>
2009-01-13 18:47 ` [linux-dvb] compiling on 2.6.28 broken? handygewinnspiel
2009-01-13 18:47 ` handygewinnspiel
2009-01-13 18:59 ` Andrew Morton
2009-01-13 19:17 ` handygewinnspiel
2009-01-13 19:37 ` Andrew Morton
2009-01-13 20:02 ` handygewinnspiel
2009-01-13 20:02 ` handygewinnspiel
2009-01-13 20:38 ` Matthew Wilcox
2009-01-14 18:29 ` Chris Mason
2009-01-14 21:19 ` wk
2009-01-14 21:24 ` Chris Mason
2009-01-14 21:35 ` Eric Sandeen
2009-01-14 21:40 ` Chris Mason
2009-01-14 23:00 ` Kay Sievers
2009-01-15 1:54 ` Chris Mason [this message]
2009-01-14 21:41 ` Eric Sandeen
2009-01-14 21:41 ` Eric Sandeen
2009-01-14 21:44 ` Andrew Morton
2009-01-14 21:48 ` Eric Sandeen
2009-01-14 21:48 ` Eric Sandeen
2009-01-14 22:57 ` Lachlan McIlroy
2009-01-14 22:57 ` Lachlan McIlroy
2009-01-18 22:06 ` Christoph Hellwig
2009-01-18 22:06 ` Christoph Hellwig
2009-01-14 21:41 ` wk
2009-01-14 22:30 ` Dave Chinner
2009-01-15 19:41 ` wk
2009-01-15 19:41 ` wk
2009-01-15 22:23 ` Dave Chinner
2009-01-10 10:27 handygewinnspiel
[not found] ` <20090110103700.107530@gmx.net>
2009-01-10 11:07 ` wk
2009-01-10 18:21 ` wk
2009-01-12 5:49 ` Mauro Carvalho Chehab
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=1231984478.8269.57.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=HWerner4@gmx.de \
--cc=akpm@linux-foundation.org \
--cc=handygewinnspiel@gmx.de \
--cc=kay.sievers@vrfy.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=mchehab@infradead.org \
--cc=rjw@sisk.pl \
--cc=sandeen@sandeen.net \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.