From: Edjunior Barbosa Machado <emachado@linux.vnet.ibm.com>
To: libc-alpha@sourceware.org, libc-ports@sourceware.org
Cc: roland@hack.frob.com, carlos@redhat.com, aj@suse.com,
naveen.n.rao@linux.vnet.ibm.com
Subject: Re: [PATCH] Update bits/siginfo.h with Linux hwpoison SIGBUS changes
Date: Wed, 22 May 2013 20:09:00 -0000 [thread overview]
Message-ID: <519D260C.9050705@linux.vnet.ibm.com> (raw)
In-Reply-To: <1368861416-26412-1-git-send-email-emachado@linux.vnet.ibm.com>
On 05/18/2013 04:16 AM, Edjunior Barbosa Machado wrote:
> On 05/16/2013 09:43 PM, Roland McGrath wrote:
>> Always write 'short int', never just 'short'. Otherwise these seem fine to
>> me (assuming they match the new kernel definitions).
>>
>> The ports changes technically need pro forma sign-off from four
>> maintainers. But I think it's good enough if you've triple-checked that
>> the new definitions match the kernel's for each machine, and wait a few
>> days to give them a chance to speak up, but go ahead and commit (say, on
>> Tuesday) for each port whose maintainer hasn't responded. You can commit
>> the common change now (and each port's change as soon as the maintainer
>> says), or wait to do them all together, at your pleasure.
>
> Here's the updated patch using 'short int' instead of just 'short'.
> I'll wait for more comments until Tuesday, following your suggestion.
I've just pushed it to master:
commit 85118d4de37e76a1596a75bae75f75f69c33225c
Author: Edjunior Barbosa Machado <emachado@linux.vnet.ibm.com>
Date: Wed May 22 14:19:49 2013 -0500
Update bits/siginfo.h with Linux hwpoison SIGBUS changes
Adds new SIGBUS error codes for hardware poison signals, syncing with
the current kernel headers (v3.9). It also adds si_trapno field for
alpha.
Thanks,
--
Edjunior
prev parent reply other threads:[~2013-05-22 20:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-07 4:47 Edjunior Barbosa Machado
2013-05-14 18:32 ` Edjunior Barbosa Machado
2013-05-14 19:38 ` Andreas Jaeger
2013-05-14 20:45 ` Carlos O'Donell
2013-05-15 6:53 ` Edjunior Barbosa Machado
2013-05-17 0:43 ` Roland McGrath
2013-05-18 7:17 ` Edjunior Barbosa Machado
2013-05-22 20:09 ` Edjunior Barbosa Machado [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=519D260C.9050705@linux.vnet.ibm.com \
--to=emachado@linux.vnet.ibm.com \
--cc=aj@suse.com \
--cc=carlos@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=libc-ports@sourceware.org \
--cc=naveen.n.rao@linux.vnet.ibm.com \
--cc=roland@hack.frob.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).