From: Andrew Morton <akpm@osdl.org>
To: "Shai Fultheim" <shai@scalex86.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Alignment for CPU maps, add padding semantics
Date: Sun, 11 Jul 2004 22:07:15 -0700 [thread overview]
Message-ID: <20040711220715.516cd475.akpm@osdl.org> (raw)
In-Reply-To: <200407112253.i6BMrEws001373@fire-2.osdl.org>
"Shai Fultheim" <shai@scalex86.org> wrote:
>
> +#define ____cacheline_pad_in_smp struct { char x; } ____cacheline_maxaligned_in_smp
anonymous structs don't work with gcc-2.95. The build emits nine
gazillion of these:
include/linux/mmzone.h:135: warning: unnamed struct/union that defines no instances
include/linux/mmzone.h:147: warning: unnamed struct/union that defines no instances
include/linux/mmzone.h:201: warning: unnamed struct/union that defines no instances
next parent reply other threads:[~2004-07-12 5:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200407112253.i6BMrEws001373@fire-2.osdl.org>
2004-07-12 5:07 ` Andrew Morton [this message]
2004-07-11 22:53 [PATCH] Alignment for CPU maps, add padding semantics Shai Fultheim
2004-07-12 8:39 ` Anton Blanchard
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=20040711220715.516cd475.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shai@scalex86.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