From: Dave Martin <Dave.Martin@arm.com>
To: Will Deacon <will.deacon@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 signalsy
Date: Fri, 9 Mar 2018 14:21:05 +0000 [thread overview]
Message-ID: <20180309142105.GS32331@e103592.cambridge.arm.com> (raw)
In-Reply-To: <20180309134818.GE15537@arm.com>
On Fri, Mar 09, 2018 at 01:48:19PM +0000, Will Deacon wrote:
> 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.
Oops, yes, just trim that off. I'd moved that changelog from the
tearoff to the top of the "cover letter" for reviewer convenience,
but guess what, there's no cover letter now I've split this patch by
itself.
[removes face from palm]
Cheers
---Dave
WARNING: multiple messages have this Message-ID (diff)
From: Dave Martin <Dave.Martin@arm.com>
To: Will Deacon <will.deacon@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 signalsy
Date: Fri, 9 Mar 2018 14:21:05 +0000 [thread overview]
Message-ID: <20180309142105.GS32331@e103592.cambridge.arm.com> (raw)
Message-ID: <20180309142105.QjsWW7WSW6KVK5H66Q1DyUvkyAECFn3hpvYMrIvjk2U@z> (raw)
In-Reply-To: <20180309134818.GE15537@arm.com>
On Fri, Mar 09, 2018 at 01:48:19PM +0000, Will Deacon wrote:
> 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.
Oops, yes, just trim that off. I'd moved that changelog from the
tearoff to the top of the "cover letter" for reviewer convenience,
but guess what, there's no cover letter now I've split this patch by
itself.
[removes face from palm]
Cheers
---Dave
next prev parent reply other threads:[~2018-03-09 14:21 UTC|newest]
Thread overview: 6+ 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-09 13:48 ` Will Deacon
2018-03-09 13:48 ` Will Deacon
2018-03-09 14:21 ` Dave Martin [this message]
2018-03-09 14:21 ` [PATCH v3] arm64: signal: Ensure si_code is valid for all fault signalsy 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=20180309142105.GS32331@e103592.cambridge.arm.com \
--to=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 \
--cc=will.deacon@arm.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