All of lore.kernel.org
 help / color / mirror / Atom feed
From: Timur Tabi <b04825@freescale.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: McClintock Matthew-B29882 <B29882@freescale.com>,
	Xu Jiucheng-B37781 <B37781@freescale.com>,
	"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH 2/2] powerpc/85xx: Create dts of each core in CAMP mode for P1021RDB-PC
Date: Wed, 11 Jul 2012 09:49:37 -0500	[thread overview]
Message-ID: <4FFD9281.1070202@freescale.com> (raw)
In-Reply-To: <4D91E39B-2773-429D-B956-38C04521C8B2@kernel.crashing.org>

Kumar Gala wrote:
> Since we already have P1021RDB-PC w/AMP support in upstream I agree we don't need another example on P1021RDB-PC.

Would you accept a patch that removes all AMP device trees from upstream?
 I just don't think that these very customer-specific dts files belong
upstream.

-- 
Timur Tabi
Linux kernel developer at Freescale

  reply	other threads:[~2012-07-11 14:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-10  8:39 [PATCH] powerpc/85xx: Add dts files for P1021RDB-PC board Xu Jiucheng
2012-07-10  8:39 ` [PATCH 2/2] powerpc/85xx: Create dts of each core in CAMP mode for P1021RDB-PC Xu Jiucheng
2012-07-10 12:25   ` Tabi Timur-B04825
2012-07-11 14:47     ` Kumar Gala
2012-07-11 14:49       ` Timur Tabi [this message]
2012-07-11 14:52         ` AW: " Schneider, Kolja
2012-07-11 14:56           ` Timur Tabi
2012-07-11 14:53         ` Kumar Gala
2012-07-11 14:56           ` Timur Tabi
2012-07-12  3:16             ` Kumar Gala
2012-07-12  3:53               ` Tabi Timur-B04825
2012-07-12  4:05                 ` Kumar Gala
2012-07-10 15:57   ` Scott Wood
2012-07-10 11:48 ` [PATCH] powerpc/85xx: Add dts files for P1021RDB-PC board Kumar Gala
2012-07-11  9:58   ` Jiucheng Xu
2012-07-11 12:31     ` Kumar Gala
2012-07-11 12:43 ` Kumar Gala

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=4FFD9281.1070202@freescale.com \
    --to=b04825@freescale.com \
    --cc=B29882@freescale.com \
    --cc=B37781@freescale.com \
    --cc=galak@kernel.crashing.org \
    --cc=linuxppc-dev@lists.ozlabs.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.