From: Christoph Hellwig <hch@lst.de>
To: Tom Rini <trini@kernel.crashing.org>
Cc: linux-mips@linux-mips.org, netdev@oss.sgi.com
Subject: Re: [PATCH 2.6.9] Export phys_cpu_present_map
Date: Wed, 20 Oct 2004 19:49:05 +0200 [thread overview]
Message-ID: <20041020174905.GA12697@lst.de> (raw)
In-Reply-To: <20041020171626.GG12544@smtp.west.cox.net>
On Wed, Oct 20, 2004 at 10:16:26AM -0700, Tom Rini wrote:
> In net/ipv6/icmp.c::icmpv6_init() there is a call to cpu_possible()
> which preprocesses down to "test_bit(((i)), (phys_cpu_present_map).bits)"
> If ipv6 is a module, phys_cpu_present_map (or cpu_possible_map which is
> defined t phys_cpu_present_map) needs to be exported.
The loop in there should be rewritten as for_each_cpu which doesn't need
this export.
next parent reply other threads:[~2004-10-20 17:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20041020171626.GG12544@smtp.west.cox.net>
2004-10-20 17:49 ` Christoph Hellwig [this message]
2004-10-20 18:16 ` [PATCH 2.6.9] Export phys_cpu_present_map Tom Rini
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=20041020174905.GA12697@lst.de \
--to=hch@lst.de \
--cc=linux-mips@linux-mips.org \
--cc=netdev@oss.sgi.com \
--cc=trini@kernel.crashing.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;
as well as URLs for NNTP newsgroup(s).