From: Randy Dunlap <rdunlap@xenotime.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
cluster-devel@redhat.com
Subject: Re: linux-next: Tree for Mar 13 (dlm / gfs2)
Date: Tue, 13 Mar 2012 10:10:36 -0700 [thread overview]
Message-ID: <4F5F7F8C.6030300@xenotime.net> (raw)
In-Reply-To: <20120313204114.e160849af7dbe5a4b4e5c0ad@canb.auug.org.au>
On 03/13/2012 02:41 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20120309:
on i386:
ERROR: "sctp_do_peeloff" [fs/dlm/dlm.ko] undefined!
GFS2_FS selects DLM (if GFS2_FS_LOCKING_DLM, which is enabled).
GFS2_FS selects IP_SCTP if DLM_SCTP, which is not enabled and not
used anywhere else in the kernel tree AFAICT.
DLM just always selects IP_SCTP.
---
~Randy
next prev parent reply other threads:[~2012-03-13 17:10 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-13 9:41 linux-next: Tree for Mar 13 Stephen Rothwell
2012-03-13 17:10 ` Randy Dunlap [this message]
2012-03-13 20:30 ` [PATCH] x86: export 'pcibios_enabled' Randy Dunlap
2012-03-13 20:30 ` Randy Dunlap
2012-03-14 0:43 ` H. Peter Anvin
2012-03-14 0:43 ` H. Peter Anvin
2012-03-14 9:29 ` Alan Cox
2012-03-14 10:59 ` Florian Tobias Schandinat
2012-03-14 11:21 ` Alan Cox
2012-03-22 0:41 ` Wang YanQing
2012-03-22 0:41 ` Wang YanQing
2012-03-26 0:27 ` Wang YanQing
2012-03-26 0:27 ` Wang YanQing
2012-03-16 0:41 ` Wang YanQing
2012-03-16 0:41 ` Wang YanQing
2012-03-19 0:30 ` Wang YanQing
2012-03-19 0:30 ` Wang YanQing
2012-03-19 1:03 ` [PATCH v2] x86: export 'pcibios_enabled' as GPL Randy Dunlap
2012-03-19 1:03 ` Randy Dunlap
2012-03-21 4:37 ` Wang YanQing
2012-03-21 4:37 ` Wang YanQing
2012-03-21 9:29 ` Alan Cox
2012-03-13 21:06 ` linux-next: Tree for Mar 13 (ata) Randy Dunlap
2012-03-13 21:22 ` Jeff Garzik
2012-03-14 0:36 ` Dan Williams
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=4F5F7F8C.6030300@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=cluster-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.