All of lore.kernel.org
 help / color / mirror / Atom feed
From: simon@nuit.ca
To: linux-kernel@vger.kernel.org
Subject: Re: problems patching XFS against current benh
Date: Mon, 23 Jun 2003 13:31:33 +0000	[thread overview]
Message-ID: <20030623133133.GE2102@nuit.ca> (raw)

> 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).
>                                                                                                                                

at first i didn't get what you meant, but then i realised, "oh, he means
only in one file should the EXPORT_SYMBOL(foo) should be mentioned".
someone on an IRC channel had mentioned that...

>> 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.

ok, cool, thanks. i wasn't sure if my changing the stsctl number was
causing it, so i had left it at 14 the second ? third ? time around...

thanks all,
eric
(feeling really dumb ATM)

-- 
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 13:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-23 13:31 simon [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-06-23 10:17 problems patching XFS against current benh simon raven
2003-06-23 11:42 ` Keith Owens

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=20030623133133.GE2102@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 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.