From: Tim Cussins <timcussins@eml.cc>
To: ALSA Development Mailing List <alsa-devel@alsa-project.org>
Subject: struct timespec as part of kernel/userspace ABI
Date: Fri, 13 Mar 2015 14:02:21 +0000 [thread overview]
Message-ID: <5502EDED.5030008@eml.cc> (raw)
Hi all,
Like the other ALSA ioctls, the proposed start_at ioctl currently uses
struct timespec.
A reviewer (of the start_at patchset) has mentioned that communicating
timespecs across the kernel/userspace boundary requires special
32bit/64bit compatibility handling (pcm_compat.c). I didn't appreciate
this :(
Should I follow the same pcm_compat.c pattern for dealing with timespecs
for the proposed start_at ioctl?
Cheers,
Tim
reply other threads:[~2015-03-13 14:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5502EDED.5030008@eml.cc \
--to=timcussins@eml.cc \
--cc=alsa-devel@alsa-project.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.