linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: David Daney <ddaney.cavm@gmail.com>
Cc: linux-mips@linux-mips.org, linux-kernel@vger.kernel.org,
	Hillf Danton <dhillf@gmail.com>,
	David Daney <david.daney@cavium.com>
Subject: Re: [PATCH] MIPS: Avoid Machine Check by flushing entire page range in huge_ptep_set_access_flags().
Date: Tue, 4 Dec 2012 16:54:46 +0100	[thread overview]
Message-ID: <20121204155446.GA19472@linux-mips.org> (raw)
In-Reply-To: <1354567466-23571-1-git-send-email-ddaney.cavm@gmail.com>

On Mon, Dec 03, 2012 at 12:44:26PM -0800, David Daney wrote:

Looks good and has survived my testing so far.  Applied.

Thanks David!

  Ralf

      reply	other threads:[~2012-12-04 15:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-03 20:44 [PATCH] MIPS: Avoid Machine Check by flushing entire page range in huge_ptep_set_access_flags() David Daney
2012-12-04 15:54 ` Ralf Baechle [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=20121204155446.GA19472@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=david.daney@cavium.com \
    --cc=ddaney.cavm@gmail.com \
    --cc=dhillf@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.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;
as well as URLs for NNTP newsgroup(s).