From: Tharre <tharre3@gmail.com>
To: Ryan Whelan <rcwhelan@gmail.com>
Cc: Matt Layher <mdlayher@gmail.com>,
WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Use of __kernel_timespec in userspace genetlink API
Date: Tue, 23 Apr 2019 01:48:13 +0200 [thread overview]
Message-ID: <20190422234813.GA19861@xultrabook.lan> (raw)
In-Reply-To: <CAM3m09SB7mhS2jqPaDWPZXg1qm65=xh=yOGQQKqx9Th833QeWQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 283 bytes --]
On 04/22, Ryan Whelan wrote:
> Sorry to be dense, but given commit c870c7a; the timespec struct will be 16
> bytes in size, regardless of the arch? 32/64bit x86 and 32/64bit ARM?
Yes, that is correct.
--
PGP fingerprint: 42CE 7698 D6A0 6129 AA16 EF5C 5431 BDE2 C8F0 B2F4
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
prev parent reply other threads:[~2019-04-22 23:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-18 14:06 Matt Layher
2019-04-22 18:13 ` Tharre
2019-04-22 23:35 ` Ryan Whelan
2019-04-22 23:48 ` Tharre [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=20190422234813.GA19861@xultrabook.lan \
--to=tharre3@gmail.com \
--cc=mdlayher@gmail.com \
--cc=rcwhelan@gmail.com \
--cc=wireguard@lists.zx2c4.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 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).