From: Andrew Morton <akpm@zip.com.au>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] per-cpu patch 1/3
Date: Sun, 21 Jul 2002 20:00:02 -0700 [thread overview]
Message-ID: <3D3B7532.96B78172@zip.com.au> (raw)
In-Reply-To: 20020718042221.8E1DA421D@lists.samba.org
Rusty Russell wrote:
>
> Name: Export __per_cpu_offset so modules can use per-cpu data.
ie: so modules can access per-cpu data which is defined in
vmlinux. afaik, modules cannot define percpu.h-style per-cpu
storage of their own, yes?
That's rather a trap. It would be nice to ensure that any
attempt to define per-cpu data in a module fails reliably
at compile-time, please.
-
next prev parent reply other threads:[~2002-07-22 2:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-18 3:46 [PATCH] per-cpu patch 1/3 Rusty Russell
2002-07-22 3:00 ` Andrew Morton [this message]
2002-07-22 5:14 ` Rusty Russell
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=3D3B7532.96B78172@zip.com.au \
--to=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@transmeta.com \
/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.