From: Matthew Wilcox <matthew@wil.cx>
To: Kyle McMartin <kyle@parisc-linux.org>
Cc: akpm@osdl.org, linux-arch@vger.kernel.org,
parisc-linux@lists.parisc-linux.org
Subject: [parisc-linux] Re: [PATCH] Generic compat_sys_sysinfo
Date: Fri, 24 Nov 2006 21:00:48 -0700 [thread overview]
Message-ID: <20061125040047.GG14076@parisc-linux.org> (raw)
In-Reply-To: <20061125014313.GD11643@athena.road.mcmartin.ca>
On Fri, Nov 24, 2006 at 08:43:13PM -0500, Kyle McMartin wrote:
> Some architectures were missing the u16 pad, however, I'm going to
> guess that a u16 is aligned on a u32 boundary and thus the padding is
> implied there...
It's more that a u32 gets aligned to a u32 boundary rather than a u16.
This is true except for m68k, which doesn't have compat.
Acked-by: Matthew Wilcox <matthew@wil.cx>
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
prev parent reply other threads:[~2006-11-25 4:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-25 1:43 [parisc-linux] [PATCH] Generic compat_sys_sysinfo Kyle McMartin
2006-11-25 4:00 ` Matthew Wilcox [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=20061125040047.GG14076@parisc-linux.org \
--to=matthew@wil.cx \
--cc=akpm@osdl.org \
--cc=kyle@parisc-linux.org \
--cc=linux-arch@vger.kernel.org \
--cc=parisc-linux@lists.parisc-linux.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