From: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
To: Guy Harris <guy-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org>,
radiotap-sUITvd46vNxg9hUCZPvPmw@public.gmane.org
Subject: Re: Endianness of particular fields?
Date: Mon, 18 Jun 2018 15:58:47 +0200 [thread overview]
Message-ID: <1529330327.3490.23.camel@sipsolutions.net> (raw)
In-Reply-To: <1519330795.2637.16.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
On Thu, 2018-02-22 at 21:19 +0100, Johannes Berg wrote:
>
> I think we should just use {u,s}{64,32,16,8} and drop the whole __le
> thing.
>
> I'd say we should just remove the wording about adopting the Linux
> convention. We'd never use __be16 or such anyway.
I removed it now, not sure why I forgot earlier. Sorry about that.
johannes
prev parent reply other threads:[~2018-06-18 13:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 18:13 Endianness of particular fields? Guy Harris
[not found] ` <83A13AAE-2089-4ED9-97D9-EDEBDD911955-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org>
2018-02-22 20:19 ` Johannes Berg
[not found] ` <1519330795.2637.16.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2018-06-18 13:58 ` Johannes Berg [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=1529330327.3490.23.camel@sipsolutions.net \
--to=johannes-cdvu00un1vgdhxzaddlk8q@public.gmane.org \
--cc=guy-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org \
--cc=radiotap-sUITvd46vNxg9hUCZPvPmw@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 NNTP newsgroup(s).