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(-)
