public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: print a fault message when attempting to write RO memory
Date: Thu, 16 Feb 2017 11:16:39 +0000	[thread overview]
Message-ID: <20170216111639.GB32039@leverpostej> (raw)
In-Reply-To: <20170216110612.GA32039@leverpostej>

On Thu, Feb 16, 2017 at 11:06:12AM +0000, Mark Rutland wrote:
> IMPORTANT NOTICE: The contents of this email and any attachments are
> confidential and may also be privileged. If you are not the intended
> recipient, please notify the sender immediately and do not disclose
> the contents to any other person, use it for any purpose, or store or
> copy the information in any medium. Thank you.

Urrgh. I messed up my client settings, and did not intend to send the
above disclaimer.

Sorry.

Mark.

  reply	other threads:[~2017-02-16 11:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-16  1:54 [PATCH] arm64: print a fault message when attempting to write RO memory Stephen Boyd
2017-02-16 11:06 ` Mark Rutland
2017-02-16 11:16   ` Mark Rutland [this message]
2017-02-16 19:06   ` Stephen Boyd

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=20170216111639.GB32039@leverpostej \
    --to=mark.rutland@arm.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox