From: David Woodhouse <dwmw2@infradead.org>
To: Jasmine Strong <jasmine@hex.linuxgrrls.org>
Cc: Allen Curtis <acurtis@onz.com>,
John Hall <John.Hall@optionexist.co.uk>,
"Linux MTD list (E-mail)" <linux-mtd@lists.infradead.org>
Subject: Re: Stable cvs version for 2.4
Date: Wed, 04 Sep 2002 16:20:22 +0100 [thread overview]
Message-ID: <6203.1031152822@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0209041551460.22265-100000@hex.linuxgrrls.org>
jasmine@hex.linuxgrrls.org said:
> > How about we add 1 byte which contains up to 8 bit fields?
> Adding a byte will destroy the alignment. you'd have to add a whole
> word.
Er, what alignment?
Either the CPU or something else assumes and requires alignment, in which
case we know that we can happily abuse the low-bit of the address.
Or it doesn't, in which case we can add our single byte and use it with
impunity. And yes, Allen's right that if we're going to add a single byte
to the structure we should just put the colour information into that
instead of using it to align the pointer so that we can abuse the low bit
of the pointer :)
--
dwmw2
next prev parent reply other threads:[~2002-09-04 15:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-03 10:09 Stable cvs version for 2.4 John Hall
2002-09-03 12:29 ` David Woodhouse
2002-09-04 0:18 ` David Woodhouse
2002-09-04 1:14 ` Jasmine Strong
2002-09-04 8:51 ` David Woodhouse
2002-09-04 14:21 ` Jasmine Strong
2002-09-04 14:37 ` David Woodhouse
2002-09-04 14:46 ` Allen Curtis
2002-09-04 14:54 ` Jasmine Strong
2002-09-04 15:17 ` Steve Wahl
2002-09-04 15:26 ` David Woodhouse
2002-09-04 15:20 ` David Woodhouse [this message]
2002-09-04 15:33 ` Jasmine Strong
2002-09-04 15:44 ` David Woodhouse
2002-09-04 15:50 ` Allen Curtis
2002-09-04 15:54 ` David Woodhouse
2002-09-04 14:49 ` Jasmine Strong
2002-09-04 15:06 ` David Woodhouse
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=6203.1031152822@redhat.com \
--to=dwmw2@infradead.org \
--cc=John.Hall@optionexist.co.uk \
--cc=acurtis@onz.com \
--cc=jasmine@hex.linuxgrrls.org \
--cc=linux-mtd@lists.infradead.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