All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob Picco <bob.picco@oracle.com>
To: sparclinux@vger.kernel.org
Subject: Re: [PATCH v2 0/8] sparc64: MM/IRQ patch queue.
Date: Mon, 29 Sep 2014 21:03:22 +0000	[thread overview]
Message-ID: <20140929210322.GG24131@zareason> (raw)
In-Reply-To: <20140927.142812.2031647355756795530.davem@davemloft.net>

Hi,
David Miller wrote:	[Mon Sep 29 2014, 04:15:43PM EDT]
> From: David Miller <davem@davemloft.net>
> Date: Sun, 28 Sep 2014 00:35:25 -0400 (EDT)
> 
> > From: Bob Picco <bpicco@meloft.net>
> > Date: Sat, 27 Sep 2014 16:46:51 -0400
> > 
> >>> Anyways, let me know how these work for you.  I'll be running tests
> >>> on my T4-2 all weekend.
> >> I'll commence with T5-2 which is local to me.
> >> 
> >> M7-4 came up with an older kernel of mine but with hardware faults.
> > 
> > Thanks in advance.
> > 
> > I added the following to my tree to deal with the MAX_BANKS issue,
> > I hope it helps the case you talked about, and it's essentially
> > free :-)
> 
> Bob, I know you're probably busy, but any updates wrt. testing
> this series?
Apologies, I've been contexting switching heavily.

My local T4-2 and T5-2 seem solid for THP "always" and large kernel parallel
makes. I've seen no issues.

There is an issue with spec-jbb. I'm hoping to have dedicated time for
this issue during the week.

I've not had time to examine the DEBUG_PAGEALLOC issue.

I'll also test M7, faults permitting.

I'll commit to resolving these issues before the merge window closes.

Obviously it is your final decision that matters.

> 
you're welcome and thanx
> Thanks.

  parent reply	other threads:[~2014-09-29 21:03 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-27 18:28 [PATCH v2 0/8] sparc64: MM/IRQ patch queue David Miller
2014-09-27 20:46 ` Bob Picco
2014-09-28  4:35 ` David Miller
2014-09-29 20:15 ` David Miller
2014-09-29 21:03 ` Bob Picco [this message]
2014-09-29 21:33 ` David Miller
2014-09-29 22:35 ` Bob Picco
2014-09-30  1:52 ` David Miller
2014-09-30  1:56 ` David Miller
2014-09-30  1:57 ` David Miller
2014-09-30  2:16 ` David Miller
2014-09-30 10:36 ` Bob Picco
2014-09-30 13:17 ` Bob Picco
2014-09-30 13:53 ` Bob Picco
2014-09-30 18:55 ` David Miller
2014-09-30 20:58 ` Bob Picco
2014-09-30 22:28 ` Bob Picco
2014-10-01  2:29 ` David Miller
2014-10-01  2:57 ` David Miller
2014-10-01 11:51 ` Bob Picco
2014-10-01 14:29 ` Bob Picco
2014-10-01 20:42 ` David Miller
2014-10-01 20:44 ` David Miller
2014-10-01 21:51 ` Bob Picco
2014-10-02 14:24 ` Bob Picco
2014-10-03 22:53 ` David Miller
2014-10-04 19:12 ` David Miller
2014-10-04 20:00 ` David Miller
2014-10-05 13:51 ` Bob Picco
2014-10-05 13:58 ` Bob Picco
2014-10-13  3:53 ` David Miller
2014-10-15  2:40 ` David Miller
2014-10-16 12:36 ` Bob Picco
2014-10-16 16:12 ` David Miller

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=20140929210322.GG24131@zareason \
    --to=bob.picco@oracle.com \
    --cc=sparclinux@vger.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 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.