public inbox for libc-ports@sourceware.org
 help / color / mirror / Atom feed
From: Andreas Jaeger <aj@suse.com>
To: Edjunior Barbosa Machado <emachado@linux.vnet.ibm.com>
Cc: libc-alpha@sourceware.org, libc-ports@sourceware.org,
	naveen.n.rao@linux.vnet.ibm.com
Subject: Re: [PATCH] Update bits/siginfo.h with Linux hwpoison SIGBUS changes
Date: Tue, 14 May 2013 19:38:00 -0000	[thread overview]
Message-ID: <519292C9.2080703@suse.com> (raw)
In-Reply-To: <1367901958-331-1-git-send-email-emachado@linux.vnet.ibm.com>

On 05/07/2013 06:45 AM, Edjunior Barbosa Machado wrote:
> This patch 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.
>
> Ok?

 > [...]
> --- a/sysdeps/unix/sysv/linux/x86/bits/siginfo.h
> +++ b/sysdeps/unix/sysv/linux/x86/bits/siginfo.h
> @@ -107,6 +107,7 @@ typedef struct
>   	struct
>   	  {
>   	    void *si_addr;	/* Faulting insn/memory ref.  */
> +	    short si_addr_lsb;	/* Valid LSB of the reported address */
We normally end comments with a "." and two spaces, see above.

Similar below and throughout the patch set. The code changes itself are 
fine.


>   	  } _sigfault;
>
>   	/* SIGPOLL.  */
> @@ -139,6 +140,7 @@ typedef struct
>   # define si_int		_sifields._rt.si_sigval.sival_int
>   # define si_ptr		_sifields._rt.si_sigval.sival_ptr
>   # define si_addr	_sifields._sigfault.si_addr
> +# define si_addr_lsb	_sifields._sigfault.si_addr_lsb
>   # define si_band	_sifields._sigpoll.si_band
>   # define si_fd		_sifields._sigpoll.si_fd
>   # define si_call_addr 	_sifields._sigsys._call_addr
> @@ -229,8 +231,12 @@ enum
>   # define BUS_ADRALN	BUS_ADRALN
>     BUS_ADRERR,			/* Non-existant physical address.  */
>   # define BUS_ADRERR	BUS_ADRERR
> -  BUS_OBJERR			/* Object specific hardware error.  */
> +  BUS_OBJERR,			/* Object specific hardware error.  */
>   # define BUS_OBJERR	BUS_OBJERR
> +  BUS_MCEERR_AR,		/* Hardware memory error: action required */

> +# define BUS_MCEERR_AR	BUS_MCEERR_AR
> +  BUS_MCEERR_AO			/* Hardware memory error: action optional */
> +# define BUS_MCEERR_AO	BUS_MCEERR_AO
>   };

The last two added comments have the same problem.
>
>   /* `si_code' values for SIGTRAP signal.  */
>

Could you update all the comments and resend, please?

Thanks,
Andreas
-- 
  Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
   SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
    GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg)
     GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126

  parent reply	other threads:[~2013-05-14 19:38 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 [this message]
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

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=519292C9.2080703@suse.com \
    --to=aj@suse.com \
    --cc=emachado@linux.vnet.ibm.com \
    --cc=libc-alpha@sourceware.org \
    --cc=libc-ports@sourceware.org \
    --cc=naveen.n.rao@linux.vnet.ibm.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).