All of lore.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will.deacon@arm.com>
To: Dave Martin <Dave.Martin@arm.com>
Cc: linux-arch@vger.kernel.org, linux-api@vger.kernel.org,
	James Morse <james.morse@arm.com>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3] arm64: signal: Ensure si_code is valid for all fault signals
Date: Fri, 9 Mar 2018 13:48:19 +0000	[thread overview]
Message-ID: <20180309134818.GE15537@arm.com> (raw)
In-Reply-To: <1520530865-26554-1-git-send-email-Dave.Martin@arm.com>

Hi Dave,

Thanks for resending this one separately -- I'll pick it up for 4.17.
Just a minor thing:

On Thu, Mar 08, 2018 at 05:41:05PM +0000, Dave Martin wrote:
> Changes since v2:
> 
>  * Rebased to v4.16-rc4.
> 
>  * Split out the SIGFPE related changes (which impact core/x86 code)
>    into a separate series.
> 
> Original blurb:

In future, please put this sort of stuff ^^ after the '---', otherwise I
have to manually remove it from the commit message when committing and
one day I'll end up forgetting.

Cheers,

Will

WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will.deacon@arm.com>
To: Dave Martin <Dave.Martin@arm.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-arch@vger.kernel.org,
	linux-api@vger.kernel.org,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	James Morse <james.morse@arm.com>
Subject: Re: [PATCH v3] arm64: signal: Ensure si_code is valid for all fault signals
Date: Fri, 9 Mar 2018 13:48:19 +0000	[thread overview]
Message-ID: <20180309134818.GE15537@arm.com> (raw)
Message-ID: <20180309134819.MFaySv355lav8Q460dvi_4gtUP1ojntwv_N_crSKJ58@z> (raw)
In-Reply-To: <1520530865-26554-1-git-send-email-Dave.Martin@arm.com>

Hi Dave,

Thanks for resending this one separately -- I'll pick it up for 4.17.
Just a minor thing:

On Thu, Mar 08, 2018 at 05:41:05PM +0000, Dave Martin wrote:
> Changes since v2:
> 
>  * Rebased to v4.16-rc4.
> 
>  * Split out the SIGFPE related changes (which impact core/x86 code)
>    into a separate series.
> 
> Original blurb:

In future, please put this sort of stuff ^^ after the '---', otherwise I
have to manually remove it from the commit message when committing and
one day I'll end up forgetting.

Cheers,

Will

WARNING: multiple messages have this Message-ID (diff)
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] arm64: signal: Ensure si_code is valid for all fault signals
Date: Fri, 9 Mar 2018 13:48:19 +0000	[thread overview]
Message-ID: <20180309134818.GE15537@arm.com> (raw)
In-Reply-To: <1520530865-26554-1-git-send-email-Dave.Martin@arm.com>

Hi Dave,

Thanks for resending this one separately -- I'll pick it up for 4.17.
Just a minor thing:

On Thu, Mar 08, 2018 at 05:41:05PM +0000, Dave Martin wrote:
> Changes since v2:
> 
>  * Rebased to v4.16-rc4.
> 
>  * Split out the SIGFPE related changes (which impact core/x86 code)
>    into a separate series.
> 
> Original blurb:

In future, please put this sort of stuff ^^ after the '---', otherwise I
have to manually remove it from the commit message when committing and
one day I'll end up forgetting.

Cheers,

Will

  reply	other threads:[~2018-03-09 13:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-08 17:41 [PATCH v3] arm64: signal: Ensure si_code is valid for all fault signals Dave Martin
2018-03-08 17:41 ` Dave Martin
2018-03-08 17:41 ` Dave Martin
2018-03-09 13:48 ` Will Deacon [this message]
2018-03-09 13:48   ` Will Deacon
2018-03-09 13:48   ` Will Deacon
2018-03-09 14:21   ` [PATCH v3] arm64: signal: Ensure si_code is valid for all fault signalsy Dave Martin
2018-03-09 14:21     ` Dave Martin
2018-03-09 14:21     ` Dave Martin

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=20180309134818.GE15537@arm.com \
    --to=will.deacon@arm.com \
    --cc=Dave.Martin@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=ebiederm@xmission.com \
    --cc=james.morse@arm.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.