From: Keith Owens <kaos@sgi.com>
To: simon@nuit.ca
Cc: linux-kernel@vger.kernel.org
Subject: Re: problems patching XFS against current benh
Date: Mon, 23 Jun 2003 21:42:40 +1000 [thread overview]
Message-ID: <17391.1056368560@firewall.ocs.com.au> (raw)
In-Reply-To: Your message of "Mon, 23 Jun 2003 10:17:51 GMT." <20030623101751.GD2102@nuit.ca>
On Mon, 23 Jun 2003 10:17:51 +0000,
simon raven <simon@nuit.ca> wrote:
>/usr/src/kernel_benh/include/linux/modules/ksyms.ver:387:1: warning: "__ver_mark_page_accessed" redefined
>In file included from /usr/src/kernel_benh/include/linux/modversions.h:100,
> from /usr/src/kernel_benh/include/linux/module.h:21,
> from exec_domain.c:14:
>/usr/src/kernel_benh/include/linux/modules/filemap.ver:7:1: warning: this is the location of the previous definition
mark_page_accessed is exported in both ksyms.c and filemap.c, both XFS
and benh add that export. Remove one of the
EXPORT_SYMBOL(mark_page_accessed).
>in include/linux/sysctl.h, two resources (?) want a VM_ set to 14:
>
>1 => VM_HEAP_STACK_GAP=14, /* int: page gap between heap and stack */
>2 => VM_PAGEBUF=14, /* struct: Control pagebuf parameters */
> VM_LAPTOP_MODE=15,
> VM_BLOCK_DUMP=16,
>
>number 1 is from benh, and number 2 is from XFS. i need both - benh's for some drivers for my hardware, and XFS
>because most of my FSes are XFS.
The sysctl numbers have nothing to do with the compile error. Pick
another number for one of the conflicting sysctls.
next prev parent reply other threads:[~2003-06-23 11:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-23 10:17 problems patching XFS against current benh simon raven
2003-06-23 11:42 ` Keith Owens [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-06-23 13:31 simon
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=17391.1056368560@firewall.ocs.com.au \
--to=kaos@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=simon@nuit.ca \
/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