linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Nicholas Piggin <npiggin@gmail.com>
To: Ley Foon Tan <ley.foon.tan@intel.com>
Cc: Guenter Roeck <linux@roeck-us.net>,
	nios2-dev@lists.rocketboards.org, linux-mm@kvack.org
Subject: Re: [RFC PATCH 01/11] nios2: update_mmu_cache clear the old entry from the TLB
Date: Tue, 2 Oct 2018 10:06:48 +1000	[thread overview]
Message-ID: <20181002100648.39389966@roar.ozlabs.ibm.com> (raw)
In-Reply-To: <1538407463.3190.1.camel@intel.com>

On Mon, 01 Oct 2018 23:24:23 +0800
Ley Foon Tan <ley.foon.tan@intel.com> wrote:

> On Sat, 2018-09-29 at 11:37 +1000, Nicholas Piggin wrote:
> > Hi,
> > 
> > Did you get a chance to look at these?
> > 
> > This first patch 1/11 solves the lockup problem that Guenter reported
> > with my changes to core mm code. So I plan to resubmit my patches
> > to Andrew's -mm tree with this patch to avoid nios2 breakage.
> > 
> > Thanks,
> > Nick  
> 
> Do you have git repo that contains these patches? If not, can you send
> them as attachment to my email?

I can do that, but it would be good to work with inline patches because
that's the usual method (rather than attached patches).

You should be able to just download or save your email and patch it,
export to mbox and `git am` it, etc. So they should be quite easy to
work with.

Thanks,
Nick

  reply	other threads:[~2018-10-02  0:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180923150830.6096-1-npiggin@gmail.com>
     [not found] ` <20180923150830.6096-2-npiggin@gmail.com>
2018-09-29  1:37   ` [RFC PATCH 01/11] nios2: update_mmu_cache clear the old entry from the TLB Nicholas Piggin
2018-10-01 15:24     ` Ley Foon Tan
2018-10-02  0:06       ` Nicholas Piggin [this message]
2018-10-03  3:52       ` Nicholas Piggin
2018-10-05  1:52         ` Ley Foon Tan
2018-10-08  7:16           ` Nicholas Piggin
2018-10-08 17:02             ` Ley Foon Tan
2018-10-08  9:21               ` Nicholas Piggin

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=20181002100648.39389966@roar.ozlabs.ibm.com \
    --to=npiggin@gmail.com \
    --cc=ley.foon.tan@intel.com \
    --cc=linux-mm@kvack.org \
    --cc=linux@roeck-us.net \
    --cc=nios2-dev@lists.rocketboards.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).