From: Ley Foon Tan <ley.foon.tan@intel.com>
To: Nicholas Piggin <npiggin@gmail.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: Fri, 05 Oct 2018 09:52:56 +0800 [thread overview]
Message-ID: <1538704376.21766.1.camel@intel.com> (raw)
In-Reply-To: <20181003135257.0b631c30@roar.ozlabs.ibm.com>
On Wed, 2018-10-03 at 13:52 +1000, Nicholas Piggin wrote:
> 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?
> Here's a tree with these patches plus 3 of the core mm code changes
> which caused nios2 to hang
>
> https://github.com/npiggin/linux/commits/nios2
>
Hi Nick
Tested your patches on the github branch. Kernel bootup and ethernet
ping are working.
Regards
Ley Foon
next prev parent reply other threads:[~2018-10-05 2:00 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
2018-10-03 3:52 ` Nicholas Piggin
2018-10-05 1:52 ` Ley Foon Tan [this message]
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=1538704376.21766.1.camel@intel.com \
--to=ley.foon.tan@intel.com \
--cc=linux-mm@kvack.org \
--cc=linux@roeck-us.net \
--cc=nios2-dev@lists.rocketboards.org \
--cc=npiggin@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.