From: James Y Knight <jyknight@google.com>
To: musl@lists.openwall.com
Subject: Re: [musl] Re: [PATCH v2] sysconf: add _SC_NPROCESSORS_CONF support
Date: Tue, 18 May 2021 13:14:44 -0400 [thread overview]
Message-ID: <CAA2zVHq9vSj1LJJb0hi5zNpu_WBu+mJAyJkseq7cpeRY8=C2zg@mail.gmail.com> (raw)
In-Reply-To: <20210518113350.GA318145@e124901.cambridge.arm.com>
[-- Attachment #1: Type: text/plain, Size: 237 bytes --]
You definitely shouldn't use "present" here; see my email from the other
thread.
On Tue, May 18, 2021 at 7:33 AM Vincent Donnefort <vincent.donnefort@arm.com>
wrote:
> Gentle ping,
>
> Any thoughts about this patch?
>
> --
> Vincent
>
[-- Attachment #2: Type: text/html, Size: 555 bytes --]
prev parent reply other threads:[~2021-05-18 17:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-06 15:31 [musl] " Vincent Donnefort
2021-05-18 11:33 ` [musl] " Vincent Donnefort
2021-05-18 17:14 ` James Y Knight [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='CAA2zVHq9vSj1LJJb0hi5zNpu_WBu+mJAyJkseq7cpeRY8=C2zg@mail.gmail.com' \
--to=jyknight@google.com \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).