From: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
To: radiotap <radiotap-rN9S6JXhQ+WXmMXjJBpWqg@public.gmane.org>
Subject: naming conventions for "fixed" and "floating" bits
Date: Thu, 19 Jun 2008 20:54:42 +0200 [thread overview]
Message-ID: <1213901682.8967.74.camel@johannes.berg> (raw)
[-- Attachment #1: Type: text/plain, Size: 397 bytes --]
Hi,
When we were discussing the namespace bits 29 and 30 we really all knew
we meant that those bits are reserved in _every_ 32-bit it_present value
like the extension flag 31, not just reserved as field numbers.
Would anybody object to adopting the naming convention that the "fixed"
bits be called "flags" and the "floating" bits be called "field
indicators", or similar?
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2008-06-19 18:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-19 18:54 Johannes Berg [this message]
[not found] ` <1213901682.8967.74.camel-YfaajirXv214zXjbi5bjpg@public.gmane.org>
2008-07-07 18:00 ` naming conventions for "fixed" and "floating" bits David Young
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=1213901682.8967.74.camel@johannes.berg \
--to=johannes-cdvu00un1vgdhxzaddlk8q@public.gmane.org \
--cc=radiotap-rN9S6JXhQ+WXmMXjJBpWqg@public.gmane.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).