All of lore.kernel.org
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev@ozlabs.org, Andy Fleming <afleming@freescale.com>,
	ddaney.cavm@gmail.com, netdev@vger.kernel.org
Subject: Re: [PATCH 1/2] powerpc/85xx: add the Fman device tree template include files
Date: Fri, 10 Aug 2012 17:37:32 -0500	[thread overview]
Message-ID: <50258D2C.5060606@freescale.com> (raw)
In-Reply-To: <50258C5D.5070108@freescale.com>

Scott Wood wrote:
> Where's the binding document for all this?  Why isn't devicetree-discuss
> on CC?

Oops.  I don't even know if our existing documentation is up-to-date.
Ugh.  I'll dig it up and post a v2.

-- 
Timur Tabi
Linux kernel developer at Freescale

      reply	other threads:[~2012-08-10 22:37 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-10 22:31 [PATCH 1/2] powerpc/85xx: add the Fman device tree template include files Timur Tabi
2012-08-10 22:31 ` [PATCH 2/2] powerpc/85xx: add Fman MDIO muxing support to the P4080DS Timur Tabi
2012-08-14 21:45   ` Kumar Gala
2012-08-14 21:45     ` Kumar Gala
2012-08-14 21:48     ` Timur Tabi
2012-08-14 21:48       ` Timur Tabi
2012-08-14 21:53       ` Scott Wood
2012-08-14 21:53         ` Scott Wood
2012-08-14 21:58         ` Timur Tabi
2012-08-14 21:58           ` Timur Tabi
2012-08-14 23:06           ` Scott Wood
2012-08-14 23:06             ` Scott Wood
2012-08-14 23:08             ` Timur Tabi
2012-08-14 23:08               ` Timur Tabi
2012-08-14 23:12               ` Scott Wood
2012-08-14 23:12                 ` Scott Wood
2012-08-10 22:34 ` [PATCH 1/2] powerpc/85xx: add the Fman device tree template include files Scott Wood
2012-08-10 22:34   ` Scott Wood
2012-08-10 22:37   ` Timur Tabi [this message]

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=50258D2C.5060606@freescale.com \
    --to=timur@freescale.com \
    --cc=afleming@freescale.com \
    --cc=ddaney.cavm@gmail.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=netdev@vger.kernel.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 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.