From: Steven Whitehouse <swhiteho@redhat.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
cluster-devel@redhat.com, David Teigland <teigland@redhat.com>
Subject: Re: linux-next: Tree for Dec 28 (gfs2)
Date: Tue, 03 Jan 2012 11:17:24 +0000 [thread overview]
Message-ID: <1325589444.2685.25.camel@menhir> (raw)
In-Reply-To: <4EFB859F.7000707@xenotime.net>
Hi,
On Wed, 2011-12-28 at 13:09 -0800, Randy Dunlap wrote:
> On 12/28/2011 01:18 AM, Stephen Rothwell wrote:
> > Hi all,
> >
> > I got bored :-( I also hate tree wide, flag day changes :-(
> >
> > Changes since 20111222:
>
>
> modular:
> ERROR: "gfs2_control_wq" [fs/gfs2/gfs2.ko] undefined!
>
> or builtin:
> main.c:(.init.text+0x313b): undefined reference to `gfs2_control_wq'
> main.c:(.exit.text+0x6a2): undefined reference to `gfs2_control_wq'
>
>
>
> Modular randconfig file is attached.
>
>
I think that might be a mistake in the dlm -next tree. The patch in
question is in the dlm tree only because that is where the prerequisites
are also. However the patch (the final one in a series of mostly dlm
related patches) is still under review, even though the prior patches
are all ready,
Steve.
prev parent reply other threads:[~2012-01-03 11:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20111228201806.d6de27fa2dbd9e3a3b7a2603@canb.auug.org.au>
2011-12-28 20:24 ` linux-next: Tree for Dec 28 (fs-writeback) Randy Dunlap
2011-12-28 21:09 ` linux-next: Tree for Dec 28 (gfs2) Randy Dunlap
2012-01-03 11:17 ` Steven Whitehouse [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=1325589444.2685.25.camel@menhir \
--to=swhiteho@redhat.com \
--cc=cluster-devel@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=sfr@canb.auug.org.au \
--cc=teigland@redhat.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;
as well as URLs for NNTP newsgroup(s).