All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
Cc: Zhang Haijun-B42677 <B42677@freescale.com>,
	"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
	"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
	"cbouatmailru@gmail.com" <cbouatmailru@gmail.com>,
	"cjb@laptop.org" <cjb@laptop.org>,
	Wood Scott-B07421 <B07421@freescale.com>,
	Fleming Andy-AFLEMING <afleming@freescale.com>,
	Zhao Chenhui-B35336 <B35336@freescale.com>
Subject: Re: [PATCH 1/4 V4] powerpc/85xx: Add support for 85xx cpu type detection
Date: Fri, 19 Jul 2013 12:20:45 -0500	[thread overview]
Message-ID: <1374254445.5357.18@snotra> (raw)
In-Reply-To: <99E897753B6F7048BD8CCDB4661D02E13DF580@039-SN2MPN1-022.039d.mgd.msft.net> (from B42677@freescale.com on Thu Jul 18 21:28:20 2013)

On 07/18/2013 09:28:20 PM, Zhang Haijun-B42677 wrote:
> Hi, scott
> 
> I had update this patch, this is the newest version.
> If there is no other problem, can you help merge this patch?
> I hope to make sure the following patch don't need to rebuild due to  
> the change of this patch.

It looks OK.  I'll pick it up when I do my next batch of patch  
application (hopefully soon).  Go ahead and send the patches that  
depend on it.

-Scott

WARNING: multiple messages have this Message-ID (diff)
From: Scott Wood <scottwood@freescale.com>
To: Zhang Haijun-B42677 <B42677@freescale.com>
Cc: Wood Scott-B07421 <B07421@freescale.com>,
	Zhao Chenhui-B35336 <B35336@freescale.com>,
	"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
	Zhang Haijun-B42677 <B42677@freescale.com>,
	Fleming Andy-AFLEMING <afleming@freescale.com>,
	"cbouatmailru@gmail.com" <cbouatmailru@gmail.com>,
	"cjb@laptop.org" <cjb@laptop.org>,
	"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH 1/4 V4] powerpc/85xx: Add support for 85xx cpu type detection
Date: Fri, 19 Jul 2013 12:20:45 -0500	[thread overview]
Message-ID: <1374254445.5357.18@snotra> (raw)
In-Reply-To: <99E897753B6F7048BD8CCDB4661D02E13DF580@039-SN2MPN1-022.039d.mgd.msft.net> (from B42677@freescale.com on Thu Jul 18 21:28:20 2013)

On 07/18/2013 09:28:20 PM, Zhang Haijun-B42677 wrote:
> Hi, scott
>=20
> I had update this patch, this is the newest version.
> If there is no other problem, can you help merge this patch?
> I hope to make sure the following patch don't need to rebuild due to =20
> the change of this patch.

It looks OK.  I'll pick it up when I do my next batch of patch =20
application (hopefully soon).  Go ahead and send the patches that =20
depend on it.

-Scott=

  reply	other threads:[~2013-07-19 17:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-17  5:12 [PATCH 1/4 V4] powerpc/85xx: Add support for 85xx cpu type detection Haijun Zhang
2013-07-17  5:12 ` Haijun Zhang
2013-07-19  2:28 ` Zhang Haijun-B42677
2013-07-19  2:28   ` Zhang Haijun-B42677
2013-07-19 17:20   ` Scott Wood [this message]
2013-07-19 17:20     ` Scott Wood
2013-07-22  1:58     ` Zhang Haijun-B42677
2013-07-22  1:58       ` Zhang Haijun-B42677

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=1374254445.5357.18@snotra \
    --to=scottwood@freescale.com \
    --cc=B07421@freescale.com \
    --cc=B35336@freescale.com \
    --cc=B42677@freescale.com \
    --cc=afleming@freescale.com \
    --cc=cbouatmailru@gmail.com \
    --cc=cjb@laptop.org \
    --cc=linux-mmc@vger.kernel.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.