All of lore.kernel.org
 help / color / mirror / Atom feed
From: jbarnes@sgi.com (Jesse Barnes)
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] Add EXPORT_SYMBOL for physical_node_map
Date: Tue, 03 Feb 2004 19:03:00 +0000	[thread overview]
Message-ID: <20040203190300.GA8216@sgi.com> (raw)
In-Reply-To: <20040203185728.GX13322@localhost>

You should probably include module.h too...

On Tue, Feb 03, 2004 at 01:57:28PM -0500, Martin Hicks wrote:
> 
> Hi David,
> 
> Can you please include this EXPORT_SYMBOL in the next release.  A few
> macros that use physical_node_map are used in modules.
> 
> Thanks
> mh
> 
> -- 
> Martin Hicks                Wild Open Source Inc.
> mort@wildopensource.com     613-266-2296

> # This is a BitKeeper generated patch for the following project:
> # Project Name: Linux kernel tree
> # This patch format is intended for GNU patch command version 2.5 or higher.
> # This patch includes the following deltas:
> #	           ChangeSet	1.1542  -> 1.1543 
> #	arch/ia64/sn/kernel/setup.c	1.28    -> 1.29   
> #
> # The following is the BitKeeper ChangeSet Log
> # --------------------------------------------
> # 04/02/03	mort@green.i.bork.org	1.1543
> # EXPORT_SYMBOL for physical_node_map.  This is required
> # for some SN2 modules.
> # --------------------------------------------
> #
> diff -Nru a/arch/ia64/sn/kernel/setup.c b/arch/ia64/sn/kernel/setup.c
> --- a/arch/ia64/sn/kernel/setup.c	Tue Feb  3 12:52:53 2004
> +++ b/arch/ia64/sn/kernel/setup.c	Tue Feb  3 12:52:53 2004
> @@ -70,6 +70,8 @@
>  
>  short physical_node_map[MAX_PHYSNODE_ID];
>  
> +EXPORT_SYMBOL(physical_node_map);
> +
>  int     numionodes;
>  
>  /*


  parent reply	other threads:[~2004-02-03 19:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-03 18:57 [PATCH] Add EXPORT_SYMBOL for physical_node_map Martin Hicks
2004-02-03 19:01 ` Christoph Hellwig
2004-02-03 19:03 ` Jesse Barnes [this message]
2004-02-03 19:04 ` Martin Hicks
2004-02-03 19:06 ` Christoph Hellwig
2004-02-10 21:51 ` David Mosberger
2004-02-10 21:58 ` Jesse Barnes
2004-02-11 21:23 ` Martin Hicks

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=20040203190300.GA8216@sgi.com \
    --to=jbarnes@sgi.com \
    --cc=linux-ia64@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.