From: Eric Wong <e@80x24.org>
To: "Nicolás Ojeda Bär" <n.oje.bar@gmail.com>
Cc: meta@public-inbox.org
Subject: [PATCH 0/2] fix SIGWINCH for Linux MIPS and PA-RISC
Date: Mon, 17 Oct 2022 09:30:51 +0000 [thread overview]
Message-ID: <20221017093053.1517046-1-e@80x24.org> (raw)
In-Reply-To: <20221015081246.18167-1-n.oje.bar@gmail.com>
Nicolás Ojeda Bär wrote:
> The logic
> hardcoding the signal number for SIGWINCH needs to be extended to handle this
> case. There may be other similar changes which are needed, but this is the only
> one I've seen so far.
Yeah, apparently two Linux architectures use n != 28 as SIGWINCH;
but *BSDs are more consistent with SIGWINCH.
1/2 was part of some ongoing unrelated work, but it's in the same area
and ready-to-go, anyways.
Eric Wong (2):
syscall: avoid needless string comparison on x86-64
sigfd: set SIGWINCH for MIPS and PA-RISC on Linux
devel/syscall-list | 2 ++
lib/PublicInbox/Sigfd.pm | 13 ++++---------
lib/PublicInbox/Syscall.pm | 22 ++++++++++++----------
t/sigfd.t | 5 ++++-
4 files changed, 22 insertions(+), 20 deletions(-)
next prev parent reply other threads:[~2022-10-17 9:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-15 8:12 SIGWINCH not recognized under macOS Nicolás Ojeda Bär
2022-10-15 8:12 ` [PATCH] SIGWINCH is 28 on macOS Nicolás Ojeda Bär
2022-10-17 8:33 ` [PATCH] SIGWINCH is 28 on Darwin-based OSes Eric Wong
2022-10-17 9:30 ` Eric Wong [this message]
2022-10-17 9:30 ` [PATCH 1/2] syscall: avoid needless string comparison on x86-64 Eric Wong
2022-10-17 9:30 ` [PATCH 2/2] sigfd: set SIGWINCH for MIPS and PA-RISC on Linux Eric Wong
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
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221017093053.1517046-1-e@80x24.org \
--to=e@80x24.org \
--cc=meta@public-inbox.org \
--cc=n.oje.bar@gmail.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://80x24.org/public-inbox.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).