From: Chris Wedgwood <cw@f00f.org>
To: "David S. Miller" <davem@redhat.com>
Cc: kiran@in.ibm.com, netdev@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: [patch] Convert sockets_in_use to use per_cpu areas
Date: Mon, 23 Dec 2002 16:00:48 -0800 [thread overview]
Message-ID: <20021224000048.GA14346@tapu.f00f.org> (raw)
In-Reply-To: <20021223.121632.105420794.davem@redhat.com>
On Mon, Dec 23, 2002 at 12:16:32PM -0800, David S. Miller wrote:
> You have to provide an explicit initializer for DEFINE_PER_CPU
> declarations or you break some platforms with older GCC's which
> otherwise won't put it into the proper section.
I wonder if "some platforms with older GCC's" will ever have these
issues resolved...
--cw
next prev parent reply other threads:[~2002-12-23 23:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-23 13:38 [patch] Convert sockets_in_use to use per_cpu areas Ravikiran G Thirumalai
2002-12-23 20:16 ` David S. Miller
2002-12-24 0:00 ` Chris Wedgwood [this message]
2002-12-24 0:23 ` David S. Miller
2002-12-24 6:48 ` Ravikiran G Thirumalai
2002-12-24 6:50 ` David S. Miller
2003-01-07 9:16 ` David S. Miller
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=20021224000048.GA14346@tapu.f00f.org \
--to=cw@f00f.org \
--cc=davem@redhat.com \
--cc=kiran@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox