From: Kumar Gala <galak@kernel.crashing.org>
To: Jia Hongtao <B38951@freescale.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2] powerpc: document the FSL MPIC message register binding
Date: Wed, 21 Mar 2012 12:22:38 -0500 [thread overview]
Message-ID: <7F5F9AA1-0976-4865-AB90-C29A6733AB6A@kernel.crashing.org> (raw)
In-Reply-To: <1330594354-31095-1-git-send-email-B38951@freescale.com>
On Mar 1, 2012, at 3:32 AM, Jia Hongtao wrote:
> This binding documents how the message register blocks found in some FSL
> MPIC implementations shall be represented in a device tree.
>
> Signed-off-by: Meador Inge <meador_inge@mentor.com>
> Signed-off-by: Jia Hongtao <B38951@freescale.com>
> ---
> Changes for v2:
> * Update compatible type from <string> to <string-list>.
> * Update interrupts description.
> * Update mpic-msgr-receive-mask description.
applied
- k
prev parent reply other threads:[~2012-03-21 17:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 9:32 [PATCH v2] powerpc: document the FSL MPIC message register binding Jia Hongtao
2012-03-21 17:22 ` Kumar Gala [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=7F5F9AA1-0976-4865-AB90-C29A6733AB6A@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=B38951@freescale.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox