From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: David Chinner <david@fromorbit.com>,
xfs@oss.sgi.com, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the xfs tree
Date: Tue, 9 Feb 2016 11:41:02 +1100 [thread overview]
Message-ID: <20160209114102.118fdc02@canb.auug.org.au> (raw)
In-Reply-To: <56B93330.20608@sandeen.net>
Hi Eric,
On Mon, 8 Feb 2016 18:30:40 -0600 Eric Sandeen <sandeen@sandeen.net> wrote:
>
> Dave just sent a patch to the xfs list to fix this,
>
> [PATCH] xfs: log recovery needs to be aware of CONFIG_XFS_RT now
Thanks. Hopefully it will be fixed in the xfs tree for linux-next
tomorrow, then,
--
Cheers,
Stephen Rothwell
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
xfs@oss.sgi.com
Subject: Re: linux-next: build failure after merge of the xfs tree
Date: Tue, 9 Feb 2016 11:41:02 +1100 [thread overview]
Message-ID: <20160209114102.118fdc02@canb.auug.org.au> (raw)
In-Reply-To: <56B93330.20608@sandeen.net>
Hi Eric,
On Mon, 8 Feb 2016 18:30:40 -0600 Eric Sandeen <sandeen@sandeen.net> wrote:
>
> Dave just sent a patch to the xfs list to fix this,
>
> [PATCH] xfs: log recovery needs to be aware of CONFIG_XFS_RT now
Thanks. Hopefully it will be fixed in the xfs tree for linux-next
tomorrow, then,
--
Cheers,
Stephen Rothwell
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2016-02-09 0:41 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-09 0:17 linux-next: build failure after merge of the xfs tree Stephen Rothwell
2016-02-09 0:17 ` Stephen Rothwell
2016-02-09 0:30 ` Eric Sandeen
2016-02-09 0:30 ` Eric Sandeen
2016-02-09 0:41 ` Stephen Rothwell [this message]
2016-02-09 0:41 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2020-07-07 0:27 Stephen Rothwell
2019-10-28 23:11 Stephen Rothwell
2019-10-28 23:18 ` Darrick J. Wong
2019-10-29 5:56 ` Christoph Hellwig
2019-10-29 6:23 ` Stephen Rothwell
2019-10-29 6:32 ` Christoph Hellwig
2019-07-01 1:12 Stephen Rothwell
2015-04-20 2:35 Stephen Rothwell
2015-04-20 2:35 ` Stephen Rothwell
2013-04-29 1:29 Stephen Rothwell
2013-04-29 1:29 ` Stephen Rothwell
2013-04-29 1:40 ` Dave Chinner
2013-04-29 1:40 ` Dave Chinner
2013-04-30 18:36 ` Ben Myers
2013-04-30 18:36 ` Ben Myers
2012-05-10 3:01 Stephen Rothwell
2012-05-10 3:01 ` Stephen Rothwell
2012-05-10 18:32 ` Ben Myers
2012-05-10 18:32 ` Ben Myers
2012-05-10 18:36 ` Mark Tinguely
2012-05-10 18:36 ` Mark Tinguely
2012-05-10 18:43 ` Ben Myers
2012-05-10 18:43 ` Ben Myers
2010-10-08 0:08 Stephen Rothwell
2010-07-26 1:51 Stephen Rothwell
2010-07-26 3:54 ` Dave Chinner
2010-07-26 4:28 ` 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=20160209114102.118fdc02@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=david@fromorbit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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 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.