All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Andrew Morton <akpm@zip.com.au>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] per-cpu patch 1/3
Date: Mon, 22 Jul 2002 15:14:04 +1000	[thread overview]
Message-ID: <20020722053036.5A26B419C@lists.samba.org> (raw)
In-Reply-To: Your message of "Sun, 21 Jul 2002 20:00:02 MST." <3D3B7532.96B78172@zip.com.au>

In message <3D3B7532.96B78172@zip.com.au> you write:
> 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.

See patch 3/3.

Cheers!
Rusty.
--
  Anyone who quotes me in their sig is an idiot. -- Rusty Russell.

      reply	other threads:[~2002-07-22  5:26 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
2002-07-22  5:14   ` Rusty Russell [this message]

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=20020722053036.5A26B419C@lists.samba.org \
    --to=rusty@rustcorp.com.au \
    --cc=akpm@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --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.