linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Luis Henriques <luis.henriques@canonical.com>
To: Michael Ellerman <michael@ellerman.id.au>
Cc: linuxppc-dev@ozlabs.org, Anton Blanchard <anton@samba.org>,
	stable@vger.kernel.org
Subject: Re: [PATCH] powerpc: fix numa distance for form0 device tree
Date: Wed, 8 May 2013 11:29:34 +0100	[thread overview]
Message-ID: <20130508102934.GA3763@hercules> (raw)
In-Reply-To: <1367898574-20594-1-git-send-email-michael@ellerman.id.au>

On Tue, May 07, 2013 at 01:49:34PM +1000, Michael Ellerman wrote:
> From: Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com>
> 
> Commit 7122beeee7bc1757682049780179d7c216dd1c83 upstream.

Thanks, I'm queuing it for the 3.5 kernel.

Cheers,
--
Luis

  parent reply	other threads:[~2013-05-08 10:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-07  3:49 [PATCH] powerpc: fix numa distance for form0 device tree Michael Ellerman
2013-05-07  4:06 ` Greg KH
2013-05-07  4:23   ` Michael Ellerman
2013-05-08 10:29 ` Luis Henriques [this message]
2013-05-09  0:04   ` Michael Ellerman
2013-05-10  4:45 ` Ben Hutchings

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=20130508102934.GA3763@hercules \
    --to=luis.henriques@canonical.com \
    --cc=anton@samba.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=michael@ellerman.id.au \
    --cc=stable@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 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).