From: Mark Rutland <mark.rutland@arm.com>
To: Will Deacon <will@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org, catalin.marinas@arm.com,
kernel-team@android.com, Robin Murphy <robin.murphy@arm.com>
Subject: Re: [PATCH] arm64: mm: decode xFSC in mem_abort_decode()
Date: Tue, 8 Jun 2021 14:55:41 +0100 [thread overview]
Message-ID: <20210608135541.GB16585@C02TD0UTHF1T.local> (raw)
In-Reply-To: <162315800528.2774193.5209202854043232051.b4-ty@kernel.org>
On Tue, Jun 08, 2021 at 02:21:52PM +0100, Will Deacon wrote:
> On Tue, 8 Jun 2021 13:37:42 +0100, Mark Rutland wrote:
> > It would be helpful if mem_abort_decode() could decode the DFSC/IFSC, as
> > this can make it easier to identify common bugs (e.g. accesses which
> > trigger alignment faults) without having to manually decode the xFSC
> > value.
> >
> > Decode the xFSC in mem_abort_decode().
>
> Applied to arm64 (for-next/mm), thanks!
>
> [1/1] arm64: mm: decode xFSC in mem_abort_decode()
> https://git.kernel.org/arm64/c/392eec313f29
Thanks!
Somehow I typo'd Robin's email address in the Cc list. If it's possible
to fix that up in the patch, that'd be great. If that's a pain, no
worries.
I'll go find a keyboard I can actually handle...
Mark.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2021-06-08 13:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 12:37 [PATCH] arm64: mm: decode xFSC in mem_abort_decode() Mark Rutland
2021-06-08 13:21 ` Will Deacon
2021-06-08 13:55 ` Mark Rutland [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=20210608135541.GB16585@C02TD0UTHF1T.local \
--to=mark.rutland@arm.com \
--cc=catalin.marinas@arm.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=robin.murphy@arm.com \
--cc=will@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox