linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: linuxppc-dev@ozlabs.org, galak@kernel.crashing.org
Subject: Re: [PATCH v3] powerpc: clean up ssi.txt, add definition for fsl, ssi-asynchronous
Date: Thu, 26 Mar 2009 10:14:23 -0500	[thread overview]
Message-ID: <ed82fe3e0903260814u1800f6a2vf067899e79198be8@mail.gmail.com> (raw)
In-Reply-To: <1236817324-24612-1-git-send-email-timur@freescale.com>

On Wed, Mar 11, 2009 at 7:22 PM, Timur Tabi <timur@freescale.com> wrote:
> Add the definition of the fsl,ssi-asynchronous property to ssi.txt (documentation
> of the device tree bindings for the Freescale SSI device).
>
> Also tidy up the layout of ssi.txt.
>
> Signed-off-by: Timur Tabi <timur@freescale.com>

Kumar, can you pick this up for 2.6.30?

-- 
Timur Tabi
Linux kernel developer at Freescale

  reply	other threads:[~2009-03-26 15:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-12  0:22 [PATCH v3] powerpc: clean up ssi.txt, add definition for fsl, ssi-asynchronous Timur Tabi
2009-03-26 15:14 ` Timur Tabi [this message]
2009-03-27 11:45 ` 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=ed82fe3e0903260814u1800f6a2vf067899e79198be8@mail.gmail.com \
    --to=timur@freescale.com \
    --cc=galak@kernel.crashing.org \
    --cc=linuxppc-dev@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 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).