linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] powerpc/p5040ds: Add support for P5040DS board
Date: Tue, 24 Jul 2012 16:47:50 -0500	[thread overview]
Message-ID: <500F1806.5040808@freescale.com> (raw)
In-Reply-To: <500F178A.6000107@freescale.com>

Scott Wood wrote:
> I thought we were specifically talking about what to set the P5040 PCIe
> compatible stringlist to.

What, I can't have two different conversations going on simultaneously in
one thread?!!?!?

:-)

Yes, we are talking about the P5040 compatible string, but earlier in this
thread, you said:

"Note that there is a version register, so perhaps we should drop the
version number from the compatible (and mention the version register in
the binding)."

and I was responding to your statement about whether we should drop the
version number.

-- 
Timur Tabi
Linux kernel developer at Freescale

  reply	other threads:[~2012-07-24 21:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-24 16:42 [PATCH] powerpc/p5040ds: Add support for P5040DS board Timur Tabi
2012-07-24 17:56 ` Scott Wood
2012-07-24 18:09   ` Timur Tabi
2012-07-24 18:32     ` Scott Wood
2012-07-24 18:55       ` Timur Tabi
2012-07-24 20:42         ` Scott Wood
2012-07-25  2:55       ` Zang Roy-R61911
2012-07-24 19:40   ` Timur Tabi
2012-07-24 20:16   ` Timur Tabi
2012-07-24 20:45   ` Timur Tabi
2012-07-24 21:19   ` Timur Tabi
2012-07-24 21:31     ` Scott Wood
2012-07-24 21:36       ` Timur Tabi
2012-07-24 21:42         ` Scott Wood
2012-07-24 21:43           ` Timur Tabi
2012-07-24 21:45             ` Scott Wood
2012-07-24 21:47               ` Timur Tabi [this message]
2012-07-24 21:54                 ` Scott Wood

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=500F1806.5040808@freescale.com \
    --to=timur@freescale.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=scottwood@freescale.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 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).