From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] trace-cmd: update to 3.1.2, add new dependencies, split kernelshark
Date: Wed, 24 Aug 2022 21:22:14 +0200 [thread overview]
Message-ID: <20220824192214.AzQwqnqUeH06YjFmqwDB4E_DA4XUc7KpMnp1MzrK6Vg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38851@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 336 bytes --]
New review comment by classabbyamp on void-packages repository
https://github.com/void-linux/void-packages/pull/38851#discussion_r954212154
Comment:
where is `cpu_set_t` put under `#ifdef _GNU_SOURCE`? `_GNU_SOURCE` does not exist anywhere in neither `sched.h` nor `cpu-set.h`. Because of this, I think `__GLIBC__` is the correct way
next prev parent reply other threads:[~2022-08-24 19:22 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 7:59 [PR PATCH] " classabbyamp
2022-08-23 8:14 ` [PR PATCH] [Updated] " classabbyamp
2022-08-23 8:22 ` classabbyamp
2022-08-23 8:28 ` classabbyamp
2022-08-23 8:31 ` classabbyamp
2022-08-23 8:47 ` [PR PATCH] [Updated] " classabbyamp
2022-08-23 8:54 ` classabbyamp
2022-08-23 8:56 ` classabbyamp
2022-08-23 8:57 ` [PR PATCH] [Updated] " classabbyamp
2022-08-23 9:11 ` classabbyamp
2022-08-23 9:13 ` classabbyamp
2022-08-23 14:37 ` sgn
2022-08-23 14:38 ` [PR REVIEW] " sgn
2022-08-23 14:39 ` sgn
2022-08-23 16:00 ` [PR PATCH] [Updated] " sgn
2022-08-23 16:16 ` sgn
2022-08-23 16:18 ` sgn
2022-08-23 16:19 ` sgn
2022-08-23 17:53 ` [PR PATCH] [Updated] " classabbyamp
2022-08-23 17:57 ` classabbyamp
2022-08-23 18:22 ` [PR PATCH] [Updated] " classabbyamp
2022-08-23 19:25 ` classabbyamp
2022-08-23 19:25 ` classabbyamp
2022-08-23 19:25 ` classabbyamp
2022-08-23 19:26 ` classabbyamp
2022-08-23 19:26 ` classabbyamp
2022-08-23 20:40 ` [PR PATCH] [Updated] " classabbyamp
2022-08-23 21:15 ` classabbyamp
2022-08-23 21:27 ` classabbyamp
2022-08-23 22:25 ` [PR PATCH] [Updated] " classabbyamp
2022-08-24 0:19 ` [PR REVIEW] " sgn
2022-08-24 0:20 ` classabbyamp
2022-08-24 0:22 ` [PR PATCH] [Updated] " classabbyamp
2022-08-24 0:23 ` [PR REVIEW] " sgn
2022-08-24 0:27 ` classabbyamp
2022-08-24 19:22 ` classabbyamp [this message]
2022-08-24 19:22 ` classabbyamp
2022-08-24 19:25 ` [PR PATCH] [Updated] " classabbyamp
2022-08-25 0:57 ` [PR REVIEW] " sgn
2022-08-25 0:59 ` sgn
2022-08-25 0:59 ` sgn
2022-08-25 1:00 ` sgn
2022-08-25 1:43 ` [PR PATCH] [Updated] " classabbyamp
2022-08-25 1:55 ` [PR REVIEW] " classabbyamp
2022-11-23 2:06 ` github-actions
2022-11-24 8:16 ` [PR PATCH] [Updated] " classabbyamp
2022-11-24 8:26 ` classabbyamp
2022-11-24 8:38 ` classabbyamp
2022-11-24 10:49 ` classabbyamp
2022-11-24 19:54 ` classabbyamp
2022-11-24 20:08 ` classabbyamp
2022-11-24 20:10 ` classabbyamp
2022-11-25 5:38 ` classabbyamp
2022-11-25 18:41 ` leahneukirchen
2022-11-26 0:35 ` classabbyamp
2022-11-26 0:35 ` [PR PATCH] [Merged]: " classabbyamp
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=20220824192214.AzQwqnqUeH06YjFmqwDB4E_DA4XUc7KpMnp1MzrK6Vg@z \
--to=classabbyamp@users.noreply.github.com \
--cc=ml@inbox.vuxu.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).