public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Emil Medve <Emilian.Medve@Freescale•com>
To: Kumar Gala <galak@codeaurora•org>
Cc: mark.rutland@arm•com, devicetree@vger•kernel.org,
	pawel.moll@arm•com, corbet@lwn•net, Geoff.Thorpe@Freescale•com,
	ijc+devicetree@hellion•org.uk, linux-doc@vger•kernel.org,
	scottwood@Freescale•com, linuxppc-dev@ozlabs•org,
	robh+dt@kernel•org, grant.likely@linaro•org
Subject: Re: [PATCH v2 2/4] dt/bindings: Introduce the FSL QorIQ DPAA BMan portal(s)
Date: Wed, 29 Oct 2014 16:26:38 -0500	[thread overview]
Message-ID: <54515B8E.50100@Freescale.com> (raw)
In-Reply-To: <044D58B4-690A-4CEA-B2DB-8AF4549D4AE2__43711.2007676207$1414507333$gmane$org@codeaurora.org>

Hello Kumar,


On 10/28/2014 09:41 AM, Kumar Gala wrote:
> On Oct 28, 2014, at 4:15 AM, Emil Medve <Emilian.Medve@freescale•com> wrote:
> 
>> Portals are memory mapped interfaces to BMan that allow low-latency,
>> lock-less interaction by software running on processor cores, accelerators
>> and network interfaces with the BMan
>>
>> Signed-off-by: Emil Medve <Emilian.Medve@Freescale•com>
>> Change-Id: I6d245ffc14ba3d0e91d403ac7c3b91b75a9e6a95
>> ---
>> .../bindings/powerpc/fsl/bman-portals.txt          | 52 ++++++++++++++++++++++
>> 1 file changed, 52 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/powerpc/fsl/bman-portals.txt
>>
>> diff --git a/Documentation/devicetree/bindings/powerpc/fsl/bman-portals.txt b/Documentation/devicetree/bindings/powerpc/fsl/bman-portals.txt
> 
> similar comment about location of binding not being PPC specific.

Will move it to Documentation/devicetree/bindings/soc

>> new file mode 100644
>> index 0000000..02e0231
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/powerpc/fsl/bman-portals.txt
>> @@ -0,0 +1,52 @@
>> +QorIQ DPAA Buffer Manager Portals Device Tree Binding
>> +
> 
> Probably worth putting the text from the commit message here as well.

Ok


Cheers,

  parent reply	other threads:[~2014-10-29 21:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-28  9:15 [PATCH v2 0/4] dt/bindings: Introduce the FSL B/QMan Emil Medve
2014-10-28  9:15 ` [PATCH v2 1/4] dt/bindings: Introduce the FSL QorIQ DPAA BMan Emil Medve
2014-10-28 14:39   ` Kumar Gala
     [not found]   ` <5DC63911-AD43-4EDA-8675-8A28EDC3F491__16064.0273978517$1414507192$gmane$org@codeaurora.org>
2014-10-29 21:16     ` Emil Medve
2014-10-28  9:15 ` [PATCH v2 2/4] dt/bindings: Introduce the FSL QorIQ DPAA BMan portal(s) Emil Medve
2014-10-28 14:41   ` Kumar Gala
     [not found]   ` <044D58B4-690A-4CEA-B2DB-8AF4549D4AE2__43711.2007676207$1414507333$gmane$org@codeaurora.org>
2014-10-29 21:26     ` Emil Medve [this message]
2014-10-28  9:15 ` [PATCH v2 3/4] dt/bindings: Introduce the FSL QorIQ DPAA QMan Emil Medve
2014-10-28  9:15 ` [PATCH v2 4/4] dt/bindings: Introduce the FSL QorIQ DPAA QMan portal(s) Emil Medve

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=54515B8E.50100@Freescale.com \
    --to=emilian.medve@freescale$(echo .)com \
    --cc=Geoff.Thorpe@Freescale$(echo .)com \
    --cc=corbet@lwn$(echo .)net \
    --cc=devicetree@vger$(echo .)kernel.org \
    --cc=galak@codeaurora$(echo .)org \
    --cc=grant.likely@linaro$(echo .)org \
    --cc=ijc+devicetree@hellion$(echo .)org.uk \
    --cc=linux-doc@vger$(echo .)kernel.org \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    --cc=mark.rutland@arm$(echo .)com \
    --cc=pawel.moll@arm$(echo .)com \
    --cc=robh+dt@kernel$(echo .)org \
    --cc=scottwood@Freescale$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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