From: Jes Sorensen <jes@linuxcare.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Alan Modra <alan@linuxcare.com.au>,
John Marvin <jsm@udlkern.fc.hp.com>,
parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] ldcw in __pthread_acquire
Date: 16 Dec 2000 22:58:56 +0100 [thread overview]
Message-ID: <d38zpgdo4f.fsf@lxplus015.cern.ch> (raw)
In-Reply-To: Matthew Wilcox's message of "Sat, 16 Dec 2000 19:29:19 +0000"
>>>>> "Matthew" == Matthew Wilcox <matthew@wil.cx> writes:
Matthew> On Fri, Dec 15, 2000 at 06:32:12PM +0100, Jes Sorensen wrote:
>> We probably cannot, we can however create our own version of the
>> header file for the parisc port.
Matthew> That was what I meant. the question is, would it _work_? Or
Matthew> is this struct embedded in other structs at
Matthew> non-16byte-aligned positions?
That can be solved by adding an aligned attribute to the struct definition.
Jes
next prev parent reply other threads:[~2000-12-16 21:58 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-15 10:12 [parisc-linux] ldcw in __pthread_acquire John Marvin
2000-12-15 11:37 ` Alan Modra
2000-12-15 16:37 ` Matthew Wilcox
2000-12-15 17:32 ` Jes Sorensen
2000-12-16 19:29 ` Matthew Wilcox
2000-12-16 21:58 ` Jes Sorensen [this message]
2000-12-17 4:31 ` Alan Modra
2000-12-17 1:22 ` Stan Sieler
2000-12-17 2:38 ` Alan Cox
2000-12-17 4:18 ` LaMont Jones
2000-12-18 0:29 ` Stan Sieler
2000-12-18 0:36 ` Alan Cox
2000-12-18 0:48 ` Stan Sieler
2000-12-18 0:59 ` Alan Cox
2000-12-18 4:43 ` LaMont Jones
2000-12-18 11:53 ` Alan Cox
2000-12-18 12:27 ` Philippe Benard
2000-12-18 14:40 ` LaMont Jones
2000-12-18 19:44 ` Stan Sieler
2000-12-18 19:54 ` Alan Cox
2000-12-18 20:15 ` Stan Sieler
2000-12-18 20:44 ` LaMont Jones
2000-12-18 21:56 ` Alan Cox
2000-12-18 22:26 ` LaMont Jones
2000-12-18 7:10 ` Philippe Benard
2000-12-18 12:06 ` Alan Cox
2000-12-18 14:49 ` LaMont Jones
2000-12-18 15:59 ` Matthew Wilcox
-- strict thread matches above, loose matches on Subject: below --
2000-12-15 10:26 John Marvin
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=d38zpgdo4f.fsf@lxplus015.cern.ch \
--to=jes@linuxcare.com \
--cc=alan@linuxcare.com.au \
--cc=jsm@udlkern.fc.hp.com \
--cc=matthew@wil.cx \
--cc=parisc-linux@thepuffingroup.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.