From: Cornelia Huck <cohuck@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: virtio@lists.oasis-open.org, virtio-dev@lists.oasis-open.org
Subject: Re: [virtio] [PATCH] introduction: add note on bitfield portability
Date: Tue, 6 Mar 2018 15:44:24 +0100 [thread overview]
Message-ID: <20180306154424.26d8e1f5.cohuck@redhat.com> (raw)
In-Reply-To: <1520346937-7968-1-git-send-email-mst@redhat.com>
On Tue, 6 Mar 2018 16:35:46 +0200
"Michael S. Tsirkin" <mst@redhat.com> wrote:
[You picked my old email address :)]
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> ---
> introduction.tex | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/introduction.tex b/introduction.tex
> index d0b770e..18ad76e 100644
> --- a/introduction.tex
> +++ b/introduction.tex
> @@ -175,5 +175,12 @@ packed by C compilers on little-endian architectures but not the
> way bitfields are packed by C compilers on big-endian
> architectures.
>
> +Assuming that CPU_TO_BE16 converts a 16-bit integer from a native
> +CPU to the big-endian byte order, the following is the equivalent
> +portable C code to generate a value in this format:
> +\begin{lstlisting}
> +CPU_TO_BE16(B << 15 | A)
> +\end{lstlisting}
> +
> \newpage
>
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
prev parent reply other threads:[~2018-03-06 14:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-06 14:35 [virtio] [PATCH] introduction: add note on bitfield portability Michael S. Tsirkin
2018-03-06 14:44 ` Cornelia Huck [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=20180306154424.26d8e1f5.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=mst@redhat.com \
--cc=virtio-dev@lists.oasis-open.org \
--cc=virtio@lists.oasis-open.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