From: DJ Delorie <dj@redhat.com>
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: libc-alpha@sourceware.org, libc-stable@sourceware.org,
andrew@sifive.com, darius@bluespec.com,
palmer@dabbelt.com
Subject: Re: [PATCH 2.27] RISC-V: fix struct kernel_sigaction to match the kernel version [BZ #23069]
Date: Mon, 01 Jan 2018 00:00:00 -0000 [thread overview]
Message-ID: <xno9ih7tm9.fsf@greed.delorie.com> (raw)
In-Reply-To: <20180417142044.GA3216@aurel32.net> (message from Aurelien Jarno on Tue, 17 Apr 2018 16:20:44 +0200)
Aurelien Jarno <aurelien@aurel32.net> writes:
> So it seems more risky to me.
I agree.
> Also note that this is not an installed header, but just a compile
> time header.
So no user-visible ABI change, good. Ok with me then :-)
next prev parent reply other threads:[~2018-04-17 15:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-01 0:00 Aurelien Jarno
2018-01-01 0:00 ` DJ Delorie
2018-01-01 0:00 ` Aurelien Jarno
2018-01-01 0:00 ` DJ Delorie [this message]
2018-01-01 0:00 ` Dmitry V. Levin
2018-01-01 0:00 ` Joseph Myers
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=xno9ih7tm9.fsf@greed.delorie.com \
--to=dj@redhat.com \
--cc=andrew@sifive.com \
--cc=aurelien@aurel32.net \
--cc=darius@bluespec.com \
--cc=libc-alpha@sourceware.org \
--cc=libc-stable@sourceware.org \
--cc=palmer@dabbelt.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.
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).