public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: simon raven <simon@nuit.ca>
To: linux-kernel@vger.kernel.org
Subject: problems patching XFS against current benh
Date: Mon, 23 Jun 2003 10:17:51 +0000	[thread overview]
Message-ID: <20030623101751.GD2102@nuit.ca> (raw)

[-- Attachment #1: Type: text/plain, Size: 1 bytes --]



[-- Attachment #2: Type: message/rfc822, Size: 2376 bytes --]

To: linux-kernel-digest@lists.us.dell.com
Subject: problems patching XFS against current benh
Date: Mon, 23 Jun 2003 04:54:06 +0000

In file included from /usr/src/kernel_benh/include/linux/modversions.h:166,
                 from /usr/src/kernel_benh/include/linux/module.h:21,
                 from exec_domain.c:14:
/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


------

i get this when i've patched current XFS patches (the new ones from today (22-06-2003)) onto benh recent rsync.

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. 

i get the same error above, even though i set VM_PAGEBUF to say 17 or 18
manually, and there's only one EXPORT_SYMBOL(mark_page_accessed) in
ksyms.h. in ksyms.ver and filemap.ver, the version symbols end up being
different (as can be seen from the above pasting). i tried twice to
change the filemap.ver number to the one that's given in ksyms.ver, and
the when the kernel image builds, it fails. 

i'm at rope's end right now, i don't know what to do. oh yeh, and i did
try on vanilla 2.4.21, and it gives me similar errors about "__ver*"
being redefined.

eric

-- 
UNIX is user friendly, it's just picky about who its friends are.          
-------------------------------------------------------------------
 ,''`.   http://www.debian.org/  | http://www.nuit.ca/           
 : :' :  Debian GNU/Linux        | http://simonraven.nuit.ca/    
 `. `'                           | PGP key ID: 6169 BE0C 0891 A038    
  `-                             | 

             reply	other threads:[~2003-06-23 10:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-23 10:17 simon raven [this message]
2003-06-23 11:42 ` problems patching XFS against current benh Keith Owens
  -- 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=20030623101751.GD2102@nuit.ca \
    --to=simon@nuit.ca \
    --cc=linux-kernel@vger.kernel.org \
    /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