From: Trevor Higgins <plan9fullfrontal@qs.co.nz>
To: 9front@9front.org
Subject: Mixfs: potential bug?
Date: Thu, 13 Feb 2020 13:06:10 +1300 [thread overview]
Message-ID: <1ba93b51-da78-8c37-f714-e354fab32b5a@qs.co.nz> (raw)
In-Reply-To: <CAF=5iUUiB5f3=6dQw6dPpneHm-kO1vOxnTWKGyaJZ37fq_ut6w@mail.gmail.com>
Looking at the code for audio/mixfs (mixfs.c)
The code uses qlock(s) where s is: struct Stream*.
In the structure ,shouldn't the QLock member of the structure be the
first member in the structure?
If not so, then why does it not matter?
Thanks.
--
next prev parent reply other threads:[~2020-02-13 0:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-12 20:51 Libpng and Zlib updates on the ports tree Lucas Francesco
2020-02-12 21:01 ` [9front] " ori
2020-02-13 0:06 ` Trevor Higgins [this message]
2020-02-13 0:21 ` [9front] Mixfs: potential bug? Silas McCroskey
2020-02-13 0:33 ` Eli Cohen
2020-02-13 1:22 ` Trevor Higgins
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=1ba93b51-da78-8c37-f714-e354fab32b5a@qs.co.nz \
--to=plan9fullfrontal@qs.co.nz \
--cc=9front@9front.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).